1 maintainer
Metadata
1 maintainer
Release files for model-card-writer 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 | |
|---|---|---|---|---|
| model_card_writer-0.1.0.tar.gz | 2.4 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| model_card_writer-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 5.0 kB
Release files / model_card_writer-0.1.0.tar.gz
| Download URL | model_card_writer-0.1.0.tar.gz |
|---|---|
| Size | 2.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a11caffe0b7a0c55ff49eef60e40cc007a9abb0862086709b38eee38916d6e4d
|
|
BLAKE2b-256 checksum How to use checksums |
e7b086600dc8fa218815b5318037a13d7fb16b3c9eac5fc9f15bf08ad893540c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.8
|
Release files / model_card_writer-0.1.0-py3-none-any.whl
| Download URL | model_card_writer-0.1.0-py3-none-any.whl |
|---|---|
| Size | 2.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9b9a6127fed9fa2a860875f89b9a6ff521dc4592a938255055d9ee238415eeb6
|
|
BLAKE2b-256 checksum How to use checksums |
132a68586e6d7164ffb3588b0feb97b4abbf259ea5e20f122196d8d659e31a9a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.8
|
Security for model-card-writer 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.
