seishub.plugins.exupery - Exupery package for SeisHub.
For more information visit http://www.seishub.org.
Release files for seishub.plugins.exupery 1.2.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 | |
|---|---|---|---|---|
| seishub.plugins.exupery-1.2.1.zip | 53.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| seishub.plugins.exupery-1.2.1-py2.7.egg | Legacy Egg format | - | - | Details |
Total release size: 135.7 kB
Release files / seishub.plugins.exupery-1.2.1.zip
| Download URL | seishub.plugins.exupery-1.2.1.zip |
|---|---|
| Size | 53.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
33fdbab91d18fc93c79a3fad2fb945c5f38acdbbb680b501be8f595743a7c412
|
|
BLAKE2b-256 checksum How to use checksums |
0bba35af238da66e5a12a98e0786223d8bb51b597212b77ba1af6df0d8bf9100
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / seishub.plugins.exupery-1.2.1-py2.7.egg
| Download URL | seishub.plugins.exupery-1.2.1-py2.7.egg |
|---|---|
| Size | 82.6 kB |
| Tags | Egg |
|
SHA-256 checksum How to use checksums |
45fba02b917eb03a79066b5ccb34f5ac0e7b1f72c8ba36c52aa5f634af69bbe7
|
|
BLAKE2b-256 checksum How to use checksums |
21fedf3b653c0c8144271421f1336071207473de6bcbc50f43e6d08717e35637
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for seishub.plugins.exupery 1.2.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.
