The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for uptimely 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 | |
|---|---|---|---|---|
| uptimely-0.0.1.tar.gz | 790 Bytes | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| uptimely-0.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 1.9 kB
Release files / uptimely-0.0.1.tar.gz
| Download URL | uptimely-0.0.1.tar.gz |
|---|---|
| Size | 790 Bytes |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1e326c2f14adb4a74083d9822a5152c6f2afee63c16393474b6d28208b82e3f9
|
|
BLAKE2b-256 checksum How to use checksums |
3b22db9cca5ee4b719f507086ba2dcc82c0540c21a9177bcbab7bbe081039021
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.12
|
Release files / uptimely-0.0.1-py3-none-any.whl
| Download URL | uptimely-0.0.1-py3-none-any.whl |
|---|---|
| Size | 1.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3527404b661822cdf27db5acfaf04fda3c1719d5777ada033bb697bef38626ba
|
|
BLAKE2b-256 checksum How to use checksums |
626858613849935be2adb70fd79c00e44bba578073f8f59a1ac8b1e2430d476f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.12
|
Security for uptimely 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.
