1 maintainer
Metadata
1 maintainer
Release files for scistackstatsdb 0.1.42
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 | |
|---|---|---|---|---|
| scistackstatsdb-0.1.42.tar.gz | 6.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| scistackstatsdb-0.1.42-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 14.0 kB
Release files / scistackstatsdb-0.1.42.tar.gz
| Download URL | scistackstatsdb-0.1.42.tar.gz |
|---|---|
| Size | 6.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5201b4580ba94ced4cfeb4d3c285f099b4a4ea3d9d34040bff79989f9e1c42a7
|
|
BLAKE2b-256 checksum How to use checksums |
5c734c90948b3ee3c80058442e44150f814fbe49d1accfaf206e27d8bfd47a34
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.11.11
|
Release files / scistackstatsdb-0.1.42-py3-none-any.whl
| Download URL | scistackstatsdb-0.1.42-py3-none-any.whl |
|---|---|
| Size | 7.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
082c7658b68eced0a33374b8d5a5529e27eb2c6ea04505d81276c1adbf5c7f19
|
|
BLAKE2b-256 checksum How to use checksums |
688a7a013a7040a10dc6bebd625c03f798db0ec3a6ff867700b02e1df277541a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.11.11
|
Security for scistackstatsdb 0.1.42
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.
