Metadata
Release files for datasets-genie 0.1.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 | |
|---|---|---|---|---|
| datasets_genie-0.1.1.tar.gz | 7.6 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| datasets_genie-0.1.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 15.7 kB
Release files / datasets_genie-0.1.1.tar.gz
| Download URL | datasets_genie-0.1.1.tar.gz |
|---|---|
| Size | 7.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
64d6c5d8d016f5e1547d68e16a00f84a08f903cca24692f77c4fa89804797018
|
|
BLAKE2b-256 checksum How to use checksums |
28e5542402e725883b5cfe05ff7822e0faebbba997d2f25099d96c4d168de45c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.3.1 CPython/3.9.16 Linux/5.15.0-1023-azure
|
Release files / datasets_genie-0.1.1-py3-none-any.whl
| Download URL | datasets_genie-0.1.1-py3-none-any.whl |
|---|---|
| Size | 8.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
69054b313246dd16a17f2c6e8598f8d154aa105296a72d3e349a8a413d760851
|
|
BLAKE2b-256 checksum How to use checksums |
3c3e1fa837667b329d0b5dab777ec148658baaa361e36956424cf6afd31f5b4f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.3.1 CPython/3.9.16 Linux/5.15.0-1023-azure
|
Security for datasets-genie 0.1.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.