1 maintainer
Metadata
1 maintainer
Release files for veridian-ozereray 0.1.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 | |
|---|---|---|---|---|
| veridian_ozereray-0.1.0.tar.gz | 2.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| veridian_ozereray-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 5.4 kB
Release files / veridian_ozereray-0.1.0.tar.gz
| Download URL | veridian_ozereray-0.1.0.tar.gz |
|---|---|
| Size | 2.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
fb1665ab7ca4edb82be2488bc4e9b5593c89b99043fd918e1c905923e3a266d0
|
|
BLAKE2b-256 checksum How to use checksums |
f0ce48c557d72814a1566a107bba63fd145b7350fccbe6904dc0b79ad4615f03
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.10.11
|
Release files / veridian_ozereray-0.1.0-py3-none-any.whl
| Download URL | veridian_ozereray-0.1.0-py3-none-any.whl |
|---|---|
| Size | 2.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7c4ea68d6260c67203df46731ee02f37941e8ff74946766e1de2b7d1f62f5ce8
|
|
BLAKE2b-256 checksum How to use checksums |
43bf7fe9d7875db0d5ebbeb46043fb4a75a39052d8d84c9e35676faa0b7ad9e5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.10.11
|
Security for veridian-ozereray 0.1.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.
