Ross ROSS = Recommend OSS · open-source software intelligence for agents

nextflow-io/nextflow

A DSL for data-driven computational pipelines observed · 2026-08-28

github.com/nextflow-io/nextflow · homepage · Groovy · Apache-2.0 (permissive) observed · 2026-08-28

Health v2 · maintenance only

97/100

  • Activity 99
  • Release rhythm 93
  • Longevity 100
How is this computed?

round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-03. Adoption (stars, forks) is never an input.

  • gap_med: 11.0
  • age_days: 4907
  • days_rel: 49
  • days_push: 7
  • n_releases_24m: 35

Full methodology

Adoption not part of the score

3475 stars · 807 forks observed · 2026-08-28

What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-29, confidence not recorded

Nextflow is an open-source DSL and runtime for building scalable, portable, and reproducible data-driven computational pipelines, based on a dataflow programming model. It executes pipelines across local machines, HPC schedulers (SLURM, SGE, LSF), and cloud platforms (AWS, Azure, Google Cloud, Kubernetes) with container-based dependency management.

Use cases

  • run reproducible bioinformatics pipelines on an HPC cluster
  • scale genomics workflows to AWS Batch or Google Cloud
  • build parallel data processing pipelines without learning a new language
  • resume a failed pipeline from the last successful step
  • run the same pipeline locally and on Kubernetes with containers
  • share and version scientific workflows with Git integration

When to choose

  • you need reproducible, containerized scientific or data-intensive pipelines
  • you want portability across HPC schedulers and multiple cloud providers
  • your workflows are parallel and dataflow-oriented with many tasks
  • you want automatic checkpointing and resume of pipeline runs

When to avoid

  • you need simple one-off scripts with no parallelism or portability needs
  • you require a GUI-based workflow builder rather than code-first DSL
  • your team is unwilling to adopt a Groovy-based DSL
  • you need lightweight orchestration for microservices rather than batch data pipelines

Facets

framework · maturity stable

workflow-automation etl container-runtime cloud scheduling developer-tools bioinformatics cloud-computing microservices cloud self-hosted jvm cli workflow-engine hpc dsl reproducibility dataflow nf-core singularity slurm aws-batch scientific-pipelines data-engineering containers automation linux macos docker kubernetes

3 sources

Member repositories

RepositoryRoleHealth v2
nextflow-io/nextflowmain97

For agents

markdown · JSON · MCP: product_card(name="nextflow-io/nextflow")

Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem