reserved for the Nemac project
1 maintainer
Metadata
1 maintainer
Release files for paneforge 0.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 | |
|---|---|---|---|---|
| paneforge-0.0.1.tar.gz | 460 Bytes | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| paneforge-0.0.1-py2.py3-none-any.whl | Python 3, Python 2 | none | any | Details |
Total release size: 1.5 kB
Release files / paneforge-0.0.1.tar.gz
| Download URL | paneforge-0.0.1.tar.gz |
|---|---|
| Size | 460 Bytes |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
91e7e89de2b023250a2375e410031a957a578e377d4bb2afdfe2a53f1f546ea4
|
|
BLAKE2b-256 checksum How to use checksums |
7e722c0a780e013a4afb6a03412080769d0b5bc525694c55ba8f42d0c798d535
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.13
|
Release files / paneforge-0.0.1-py2.py3-none-any.whl
| Download URL | paneforge-0.0.1-py2.py3-none-any.whl |
|---|---|
| Size | 1.0 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
6e0d3388321b9eb61d2e00ec3cc1f5acc5bb7af2517b23452858412ce6df05a6
|
|
BLAKE2b-256 checksum How to use checksums |
f5bfec3f81bcacad4d95461b1ab0a146678bde8479d51719cb231b98800991ea
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.13
|
Security for paneforge 0.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.
