The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for napari-plugin 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 | |
|---|---|---|---|---|
| napari_plugin-0.1.0.tar.gz | 2.6 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| napari_plugin-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 6.3 kB
Release files / napari_plugin-0.1.0.tar.gz
| Download URL | napari_plugin-0.1.0.tar.gz |
|---|---|
| Size | 2.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e3dbcc0d4238410e8d1914f71fee6e00c9fd858c33049370d037429264eac5dc
|
|
BLAKE2b-256 checksum How to use checksums |
bb904b16a0f8e4fcbb43eaa6712025ab9f7c4d9a083a0e74f177f84606de169d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.11.4
|
Release files / napari_plugin-0.1.0-py3-none-any.whl
| Download URL | napari_plugin-0.1.0-py3-none-any.whl |
|---|---|
| Size | 3.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
325d5aa5d5c6a8cdf6b9481750271c41f15c92dc965c7ebadd5680e4a4ae43f8
|
|
BLAKE2b-256 checksum How to use checksums |
a46b069ad57a3cf0ea2519477395e2f913077648d96931b39db7f051662e320d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.11.4
|
Security for napari-plugin 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.
