The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for nextup 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 | |
|---|---|---|---|---|
| nextup-0.1.0.tar.gz | 1.9 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| nextup-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 4.0 kB
Release files / nextup-0.1.0.tar.gz
| Download URL | nextup-0.1.0.tar.gz |
|---|---|
| Size | 1.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
00baeda2ef28d24150179ef085c7d9e3714635eba39870719a98def597d7e5cd
|
|
BLAKE2b-256 checksum How to use checksums |
8ced430856a0faa5f1d2ae8cda30568ebc8c209bba65c43c915ccb05cf164c46
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.1.13 CPython/3.10.1 Windows/10
|
Release files / nextup-0.1.0-py3-none-any.whl
| Download URL | nextup-0.1.0-py3-none-any.whl |
|---|---|
| Size | 2.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
12c648128c55ea56bb57cab87930153bcdf789a937c632107341692ecaefbd32
|
|
BLAKE2b-256 checksum How to use checksums |
3b73ed76d820c6840bfb15ba23abc35ed07513a6c9a203b790f72c61b99dc73e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.1.13 CPython/3.10.1 Windows/10
|
Security for nextup 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.
