seishub.plugins.seismology - Seismology package for SeisHub.
For more information visit http://www.seishub.org.
Metadata
Release files for seishub.plugins.seismology 1.2.2
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.seismology-1.2.2.zip | 1.7 MB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| seishub.plugins.seismology-1.2.2-py2.7.egg | Legacy Egg format | - | - | Details |
Total release size: 3.4 MB
Release files / seishub.plugins.seismology-1.2.2.zip
| Download URL | seishub.plugins.seismology-1.2.2.zip |
|---|---|
| Size | 1.7 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
28b273bfa1b4c31fb4964e10e0d7692fad04753e3a7bcb33c916baa35cf2b6a7
|
|
BLAKE2b-256 checksum How to use checksums |
cb0ae39742559c87d94f39c8b4d45a286ca89edc5bd5c299c7f63fe11fc13a7c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / seishub.plugins.seismology-1.2.2-py2.7.egg
| Download URL | seishub.plugins.seismology-1.2.2-py2.7.egg |
|---|---|
| Size | 1.7 MB |
| Tags | Egg |
|
SHA-256 checksum How to use checksums |
2e9d534427602aea261b5e5f026602f7500c6e6a0228a9d714053e2afa4e31aa
|
|
BLAKE2b-256 checksum How to use checksums |
bb542a88041985250e02eafd4ecccf41f402c7ebffb87bb50249c1abc7552ab5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for seishub.plugins.seismology 1.2.2
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.