The author of this package has not provided a project description
2 maintainers
Metadata
2 maintainers
Release files for up-pyperplan 1.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 | |
|---|---|---|---|---|
| up_pyperplan-1.1.0.tar.gz | 11.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| up_pyperplan-1.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 24.2 kB
Release files / up_pyperplan-1.1.0.tar.gz
| Download URL | up_pyperplan-1.1.0.tar.gz |
|---|---|
| Size | 11.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1c9c1f5c5113cd132d57f35abfeae6d416d3a2b613059e02fc8a363d4052869f
|
|
BLAKE2b-256 checksum How to use checksums |
5fa561322d7cf44316fef93bc78d4bfb32d9958107d4bb4b4e01f5992cd72356
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.9.18
|
Release files / up_pyperplan-1.1.0-py3-none-any.whl
| Download URL | up_pyperplan-1.1.0-py3-none-any.whl |
|---|---|
| Size | 12.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e5a7d4ee940481c2f071cec17b73714f49cd65a7c31c9988fae4a5010a762f9e
|
|
BLAKE2b-256 checksum How to use checksums |
cb91579f9a35c4f73073aa59f8ca0e408c7f9b6fe668587022e26c82d63c4481
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.9.18
|
Security for up-pyperplan 1.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.
