1 maintainer
Metadata
1 maintainer
Release files for battlecatseditor 1.0.2
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 | |
|---|---|---|---|---|
| battlecatseditor-1.0.2.tar.gz | 165.5 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| battlecatseditor-1.0.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 381.9 kB
Release files / battlecatseditor-1.0.2.tar.gz
| Download URL | battlecatseditor-1.0.2.tar.gz |
|---|---|
| Size | 165.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
722c25c5593de23b0d3d97cd9d2ea4cafccdd6f904ec61c101c9be1812f408ee
|
|
BLAKE2b-256 checksum How to use checksums |
dfa45286cda22f09ea3841916dffdb769663a9f583a5b027cb00882e86537e34
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.12
|
Release files / battlecatseditor-1.0.2-py3-none-any.whl
| Download URL | battlecatseditor-1.0.2-py3-none-any.whl |
|---|---|
| Size | 216.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
84dfeaae5e7dcefff9047970acc79d148fa4ec35b6cdfba9665e55e5cbc46e7b
|
|
BLAKE2b-256 checksum How to use checksums |
25150b456c215ae87c7eff0d24756cf0c0f1da369f9bc21ead6403c049ddc679
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.12
|
Security for battlecatseditor 1.0.2
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.
