The author of this package has not provided a project description
Metadata
Release files for morse-tunes 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 | |
|---|---|---|---|---|
| morse_tunes-0.1.0.tar.gz | 2.2 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| morse_tunes-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 5.1 kB
Release files / morse_tunes-0.1.0.tar.gz
| Download URL | morse_tunes-0.1.0.tar.gz |
|---|---|
| Size | 2.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
cb57bb82dec7d02eeedbe9242b58d6a510dae21c347a855327e143d9fd6b3d1a
|
|
BLAKE2b-256 checksum How to use checksums |
1f1da4719eb5c4cc341d8dea7924b66a36eeacc737c2ccebd01f282a7fcf8877
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.0.1 CPython/3.12.7
|
Release files / morse_tunes-0.1.0-py3-none-any.whl
| Download URL | morse_tunes-0.1.0-py3-none-any.whl |
|---|---|
| Size | 2.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
4497904476bec42ac06ba5409f83c9737bc40e26760c5cffd0038b0436797b49
|
|
BLAKE2b-256 checksum How to use checksums |
34daf3817689ddf6bb7f0280b9ce44c33013f23311ebd81907d232340caf16f1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.0.1 CPython/3.12.7
|
Security for morse-tunes 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.