The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for necoherence 0.2.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 | |
|---|---|---|---|---|
| necoherence-0.2.0.tar.gz | 92.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| necoherence-0.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 155.1 kB
Release files / necoherence-0.2.0.tar.gz
| Download URL | necoherence-0.2.0.tar.gz |
|---|---|
| Size | 92.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7db33691baca4f393e58144a4802703eb87b9050ef247f17361b2bd293a7772f
|
|
BLAKE2b-256 checksum How to use checksums |
e5db22c5798b943fc55e9d5b037ddeb0d13cb2065b6a5ae0aeb846d520628c5d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.13
|
Release files / necoherence-0.2.0-py3-none-any.whl
| Download URL | necoherence-0.2.0-py3-none-any.whl |
|---|---|
| Size | 62.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
66c7e291664340df7f235f84337a907baca9b8bfffe90df508c0ccf785120bb9
|
|
BLAKE2b-256 checksum How to use checksums |
a431b7f13b684b95091f061f49d7bcd18c5396cc78de44fe36f00b964406238c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.13
|
Security for necoherence 0.2.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.
