1 maintainer
Metadata
1 maintainer
Release files for nexus-fitness 2.0.5
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 | |
|---|---|---|---|---|
| nexus_fitness-2.0.5.tar.gz | 26.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| nexus_fitness-2.0.5-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 52.3 kB
Release files / nexus_fitness-2.0.5.tar.gz
| Download URL | nexus_fitness-2.0.5.tar.gz |
|---|---|
| Size | 26.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9f1b9f346d5a67a380e7d94e841ee97fc34693bc20ff7991740f402712664dab
|
|
BLAKE2b-256 checksum How to use checksums |
98e58ab4739e4fdf0b956d5adf9e295887ca18bb5851da68a92fff97cc323e67
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.6.14
|
Release files / nexus_fitness-2.0.5-py3-none-any.whl
| Download URL | nexus_fitness-2.0.5-py3-none-any.whl |
|---|---|
| Size | 26.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
6460e2dd5dd795749c130e4c0ab54c1f3b06fb42b9c6f4b6252651eda3b775b9
|
|
BLAKE2b-256 checksum How to use checksums |
c0c4b0c01fae443c45cb31a40670d288b5383105c5c2a94f1f128d088056a960
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.6.14
|
Security for nexus-fitness 2.0.5
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.
