The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for clipnotes 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 | |
|---|---|---|---|---|
| clipnotes-0.1.0.tar.gz | 1.5 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| clipnotes-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 2.7 kB
Release files / clipnotes-0.1.0.tar.gz
| Download URL | clipnotes-0.1.0.tar.gz |
|---|---|
| Size | 1.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f48e6f97ca4cece986683c864c4d30e59643cf3a34bf0d9a5f95a941df48f705
|
|
BLAKE2b-256 checksum How to use checksums |
70e871212baf49e929e1aa26f16f47266dc051bc8e127b98a6129c54a5c64e33
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.0.0 CPython/3.12.3
|
Release files / clipnotes-0.1.0-py3-none-any.whl
| Download URL | clipnotes-0.1.0-py3-none-any.whl |
|---|---|
| Size | 1.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d169add750aaa8bf5d135627ec0b707172559e20176d395560f8b863b9e93eac
|
|
BLAKE2b-256 checksum How to use checksums |
5bf5184353a13b8e8068c2501219a2786a68fc2985ac77e035687c028cb614b4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.0.0 CPython/3.12.3
|
Security for clipnotes 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.
