1 maintainer
Metadata
1 maintainer
Release files for zlgcan-driver-py 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 | |
|---|---|---|---|---|
| zlgcan_driver_py-0.1.0.tar.gz | 1.2 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| zlgcan_driver_py-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 2.6 kB
Release files / zlgcan_driver_py-0.1.0.tar.gz
| Download URL | zlgcan_driver_py-0.1.0.tar.gz |
|---|---|
| Size | 1.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b1c45e4a4b774f55f054ad697b732f62bc759ae20215a4c3a78741213337c377
|
|
BLAKE2b-256 checksum How to use checksums |
e361f2e6489e6450703f209d94092f94f2c85a069017a4026a21044250b884ae
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.12.3
|
Release files / zlgcan_driver_py-0.1.0-py3-none-any.whl
| Download URL | zlgcan_driver_py-0.1.0-py3-none-any.whl |
|---|---|
| Size | 1.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b9947168bccb7b56ce319c736b35e3d2d5b091d17fc12b30547fb7c43b76066b
|
|
BLAKE2b-256 checksum How to use checksums |
c3589525805b1d47e1d31dfd1c475d365d5a3d46a7fe093eb6f43b6e39d64e51
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.12.3
|
Security for zlgcan-driver-py 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.
