The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for abandoned-tron 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 | |
|---|---|---|---|---|
| abandoned_tron-0.1.tar.gz | 872 Bytes | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| abandoned_tron-0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 2.0 kB
Release files / abandoned_tron-0.1.tar.gz
| Download URL | abandoned_tron-0.1.tar.gz |
|---|---|
| Size | 872 Bytes |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2fdc4cadd00aa723789685800eab98b3116fbeee7df4d1e89a2be2f15c1a59b2
|
|
BLAKE2b-256 checksum How to use checksums |
2d7cbc411d4c4b9206669b2a26f10afc85a1c410d356a78b88dcc9b3f2006031
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.4
|
Release files / abandoned_tron-0.1-py3-none-any.whl
| Download URL | abandoned_tron-0.1-py3-none-any.whl |
|---|---|
| Size | 1.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c184c8ce141bcf4e786ee3308bb09f7cdf71159376e703ffe5a52f8c56de7314
|
|
BLAKE2b-256 checksum How to use checksums |
ba737bfe30d3b9f58a2024a1c19bbeaebb0fc364a75c0319c7dc4f64fa748c14
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.4
|
Security for abandoned-tron 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.
