The author of this package has not provided a project description
Metadata
Release files for schemas-hf 0.1.3
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 | |
|---|---|---|---|---|
| schemas_hf-0.1.3.tar.gz | 49.8 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| schemas_hf-0.1.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 114.8 kB
Release files / schemas_hf-0.1.3.tar.gz
| Download URL | schemas_hf-0.1.3.tar.gz |
|---|---|
| Size | 49.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f9f322e089e5197f06b067bd06a7a9fc51886a5b265ad49cd2753f0c353abb82
|
|
BLAKE2b-256 checksum How to use checksums |
1d5646e987e2a1a01a4ffcf72ad407f0f9d69c659da4aa2683a3946928a6784c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.11.13
|
Release files / schemas_hf-0.1.3-py3-none-any.whl
| Download URL | schemas_hf-0.1.3-py3-none-any.whl |
|---|---|
| Size | 65.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2147d4d7f9548cdb5841a6c9557d05e50bd1d83d89592caa171d4cf73c851dd0
|
|
BLAKE2b-256 checksum How to use checksums |
11c746bba0461cee07ec56f3541408e2f908513b8bbf298a62342e72bb85edf2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.11.13
|
Security for schemas-hf 0.1.3
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.