The author of this package has not provided a project description
Metadata
Release files for awesome-library 1.3.3
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 | |
|---|---|---|---|---|
| awesome_library-1.3.3.tar.gz | 1.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| awesome_library-1.3.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 3.8 kB
Release files / awesome_library-1.3.3.tar.gz
| Download URL | awesome_library-1.3.3.tar.gz |
|---|---|
| Size | 1.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a5e4dbe98a643ddcb192525278f4d887ed640c85cd892490af58c35026acfb0b
|
|
BLAKE2b-256 checksum How to use checksums |
5d1587b57330f185858429a33cd1c5e993c6723b3d0688b6059145ea6fb33341
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.6.1 CPython/3.11.5 Darwin/22.5.0
|
Release files / awesome_library-1.3.3-py3-none-any.whl
| Download URL | awesome_library-1.3.3-py3-none-any.whl |
|---|---|
| Size | 2.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c2a472926068babd501f7f07803634b8585488121931aa0c15f58e53fef86fe0
|
|
BLAKE2b-256 checksum How to use checksums |
f7c93fd06841a9d6cad6c291fa4e906af4cb1789082c80266a5b0ceeb16310dd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.6.1 CPython/3.11.5 Darwin/22.5.0
|
Security for awesome-library 1.3.3
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.