Metadata
Release files for dodecahedron 0.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 | |
|---|---|---|---|---|
| dodecahedron-0.0.5.tar.gz | 41.2 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| dodecahedron-0.0.5-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 125.2 kB
Release files / dodecahedron-0.0.5.tar.gz
| Download URL | dodecahedron-0.0.5.tar.gz |
|---|---|
| Size | 41.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b13c56245f5caf2637c02765d2903ffcf3effec15fb258ffd1c6711ac2f8dbdd
|
|
BLAKE2b-256 checksum How to use checksums |
0c6afb38e3825e1fd01fe5332740a7ceade095b04e2a4a191376ad88da7bed3f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.4
|
Release files / dodecahedron-0.0.5-py3-none-any.whl
| Download URL | dodecahedron-0.0.5-py3-none-any.whl |
|---|---|
| Size | 83.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d7a513db3f2b85da096de0894086819e1478668a050adcddef989901d567ce34
|
|
BLAKE2b-256 checksum How to use checksums |
44f2bd1a1ef5edfa553712b939346b37da79b9b6a524af15706e47b4a1ecee3e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.4
|
Security for dodecahedron 0.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.