Metadata
Release files for sugardatty 0.0.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 | |
|---|---|---|---|---|
| sugardatty-0.0.1.tar.gz | 4.2 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| sugardatty-0.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 5.6 kB
Release files / sugardatty-0.0.1.tar.gz
| Download URL | sugardatty-0.0.1.tar.gz |
|---|---|
| Size | 4.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6fef9eb0c13bf65b8239efaf91dcff63c49caae03e0dd3389c0c3d0717421138
|
|
BLAKE2b-256 checksum How to use checksums |
e5a6b7d02cf91ce2564554d6f121d2e58800ccb7f2481e939db86fcb49e99ebe
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Release files / sugardatty-0.0.1-py3-none-any.whl
| Download URL | sugardatty-0.0.1-py3-none-any.whl |
|---|---|
| Size | 1.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
923317f1f5a0198553e209baed4fbdf18295c1393278b7588dc7a758ecd46f6b
|
|
BLAKE2b-256 checksum How to use checksums |
27cd439405e78df6be0c9fa3d71ff75e9d0eb1cc475d4024186655467d6858b0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Security for sugardatty 0.0.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.