The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for mikroj 0.1.20
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 | |
|---|---|---|---|---|
| mikroj-0.1.20.tar.gz | 10.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| mikroj-0.1.20-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 24.4 kB
Release files / mikroj-0.1.20.tar.gz
| Download URL | mikroj-0.1.20.tar.gz |
|---|---|
| Size | 10.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2f8a37eef7fc88235f6e708441d947cba1c2dc5c0a98ab3031c4bfbb303e7198
|
|
BLAKE2b-256 checksum How to use checksums |
98785fec4c1b0dbd24715e24f80710c272128b0e4e58c8a01519ce53c4ada708
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.4.0 CPython/3.10.6 Linux/5.19.0-41-generic
|
Release files / mikroj-0.1.20-py3-none-any.whl
| Download URL | mikroj-0.1.20-py3-none-any.whl |
|---|---|
| Size | 13.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
fbbbc6154f22c4af4edef0c630b1d57753850595365fa8815a6b31a08b890800
|
|
BLAKE2b-256 checksum How to use checksums |
17bc8ec04a023d93e6ae35ec9f5d41d3f94bcd8b8b4afa87189ee95671ca3073
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.4.0 CPython/3.10.6 Linux/5.19.0-41-generic
|
Security for mikroj 0.1.20
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.
