1 maintainer
Metadata
1 maintainer
Release files for json2gbnf 0.0.4
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 | |
|---|---|---|---|---|
| json2gbnf-0.0.4.tar.gz | 6.5 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| json2gbnf-0.0.4-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 13.8 kB
Release files / json2gbnf-0.0.4.tar.gz
| Download URL | json2gbnf-0.0.4.tar.gz |
|---|---|
| Size | 6.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
60a34ba32baf52fffb1f768bd1ce838c0f8c648e5738c82e863c5c4f696271a8
|
|
BLAKE2b-256 checksum How to use checksums |
7cd2c46bdfcc4bbb9996da8e20a2d773815dca5abaa4a928cf94db05c060ea64
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/4.0.2 CPython/3.11.9
|
Release files / json2gbnf-0.0.4-py3-none-any.whl
| Download URL | json2gbnf-0.0.4-py3-none-any.whl |
|---|---|
| Size | 7.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f81ac9a48c15e478048694d0117c7df3b6c8a56ed52d3529c256fd4e1ee00ea0
|
|
BLAKE2b-256 checksum How to use checksums |
5e360c57e3ec5fd9a6e1f7c71ae6195709cd2ae25690ea53ad0ec4d849727510
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/4.0.2 CPython/3.11.9
|
Security for json2gbnf 0.0.4
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.
