The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for dianoia 0.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 | |
|---|---|---|---|---|
| dianoia-0.1.0.tar.gz | 551 Bytes | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| dianoia-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 1.6 kB
Release files / dianoia-0.1.0.tar.gz
| Download URL | dianoia-0.1.0.tar.gz |
|---|---|
| Size | 551 Bytes |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
13febb0444d47cf7a3bbfe85b199071367bfb1ca74e84393fbbfeca7132f3ea5
|
|
BLAKE2b-256 checksum How to use checksums |
4ac9c8f53c4b167ca8ad3de85d110a95763d71e85dc67ce417fc2e4c2b6fe82c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.12
|
Release files / dianoia-0.1.0-py3-none-any.whl
| Download URL | dianoia-0.1.0-py3-none-any.whl |
|---|---|
| Size | 1.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c22d67a63b406ef2fa240387555be7a008180d05301721bccd6670391844bd01
|
|
BLAKE2b-256 checksum How to use checksums |
16e1b60630a9807369dade99080bc266a8b9c242e295be216b406b1b66f55c79
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.12
|
Security for dianoia 0.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.
