The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for macicons 0.1.1
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 | |
|---|---|---|---|---|
| macicons-0.1.1.tar.gz | 512.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| macicons-0.1.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 1.0 MB
Release files / macicons-0.1.1.tar.gz
| Download URL | macicons-0.1.1.tar.gz |
|---|---|
| Size | 512.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6750df12f69a637c557ffc7fcad058146451f1558b82a8063e59e169fa55bebd
|
|
BLAKE2b-256 checksum How to use checksums |
f02888e4ff89a3a42b2bfd725123052cde768abb7d4fd3e70146e5da922b9a6a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.10.10
|
Release files / macicons-0.1.1-py3-none-any.whl
| Download URL | macicons-0.1.1-py3-none-any.whl |
|---|---|
| Size | 513.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
19963f68a4a3379635f4106a57e3d302068d135ebf80529db7e342f547a36917
|
|
BLAKE2b-256 checksum How to use checksums |
05f76b31d9dfb22a3d64bfa900df6f91a36f77fd4e23d64ec4edd09ba95bb62a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.10.10
|
Security for macicons 0.1.1
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.
