This release is a pre-release and may not be stable for production use.
everyome-pipelines
The Nextflow pipelines that Everyome modules use (nf-core/rnaseq 3.27.0, nf-core/scrnaseq 4.2.0, nf-core/genomeassembler 2.0.1, nf-core/bacass 2.6.1 and nf-core/proteinfold 2.0.0), with the Nextflow plugins they need, pinned to exact releases and checked by SHA-256. Install it next to Everyome:
pip install "everyome[all]==0.1.0a3" "everyome-pipelines==0.1.0a3"
When you press Run, Everyome copies the pipeline to your cluster once, checks
it there, and runs that copy offline. See Everyome's docs/PIPELINES.md.
Building (maintainers): python -m everyome.core.pipelines build --into pipelines/everyome_pipelines/bundles,
then python -m build pipelines. The build fails if anything fetched differs from the pinned checksums.
1 maintainer
Metadata
1 maintainer
Release files for everyome-pipelines 0.1.0a5
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 | Actions |
|---|---|---|---|---|
| everyome_pipelines-0.1.0a5.tar.gz | 30.2 MB | With provenance | Details for everyome_pipelines-0.1.0a5.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| everyome_pipelines-0.1.0a5-py3-none-any.whl | Python 3 | none | any | Details for everyome_pipelines-0.1.0a5-py3-none-any.whl |
Total release size: 60.4 MB
Release files / everyome_pipelines-0.1.0a5.tar.gz
| Download URL | everyome_pipelines-0.1.0a5.tar.gz |
|---|---|
| Size | 30.2 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f1a65cf4b5fdf60f0542fcc7951576622d78c9a3154299898c85200662ed3f2b
|
|
BLAKE2b-256 checksum How to use checksums |
83b8b8a5446a7a2e99b318b19496a67efbcf7d227bc3600346385eb2159d6ab5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 4, 2026.
Transparency logRelease files / everyome_pipelines-0.1.0a5-py3-none-any.whl
| Download URL | everyome_pipelines-0.1.0a5-py3-none-any.whl |
|---|---|
| Size | 30.2 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
56218a2a34d371e427b33b700f19be473f4a697c3a3d5586934d558f2dd041ee
|
|
BLAKE2b-256 checksum How to use checksums |
51b1fb4f7b00ee6d75fafe7cda64199235cbe902cb3aa0bdc56835e8ca3d9c46
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 4, 2026.
Transparency logSecurity for everyome-pipelines 0.1.0a5
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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for everyome_pipelines-0.1.0a5.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 4, 2026.
Transparency logA 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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
