Our open peer review process makes scientific software better and easier to discover. Check out our accepted packages.

How Python software peer review works

A pencil sketch of a round table with people sitting around it from different backgrounds working on laptops and also writing together.

Software peer review, similar to the review of scientific papers, is a process where scientists vet software code, documentation and infrastructure. pyOpenSci leads an open peer review process run by a community of dedicated volunteers. Reviews are supportive and fully transparent with the shared goal of improving the quality, usability and maintainability of the software that is driving open science.

  • Diverse teams lead each review, enhancing the overall feedback quality.

Learn more about the peer review timeline and roles

Get a fast-track JOSS publication

A pencil sketch of a round table with people sitting around it from different backgrounds working on laptops and also writing together.

Our partnership with JOSS means that you don’t have to choose between pyOpenSci and JOSS. Simply submit your package to pyOS for review. If your package is accepted and in scope for JOSS, it will be fast-tracked through JOSS’ review process.

Learn more about our JOSS partnership

Scientists need trusted and vetted software

A pencil sketch of a round table with people sitting around it from different backgrounds working on laptops and also writing together.

Through our partnerships with domain specific communities our catalog of trusted tools for scientists across domains continues to grow.

Learn more about scientific Python community partnerships

Peer review benefits open source maintainers

A pencil sketch of a round table with people sitting around it from different backgrounds working on laptops and also writing together.

The pyOpenSci peer review process multiplies shared knowledge, making it easier for Pythonistas of all levels to accomplish challenging tasks, such as navigating the Python packaging ecosystem, with relative ease. And our diverse community supports scientific package maintainers in their efforts to develop and build robust software.

Learn more about the benefits of peer review

Get involved with software peer review

Become a pyOpenSci reviewer

We could use your help! Fill out our reviewer form. We will contact you if we have a package that we need reviewers for. It’s OK if you’ve never reviewed a package before! We’ll walk you through it.

See Our Review Process in Action

Our software review process is run using GitHub issues. This means that anyone can check in on any part of any review and read all of the conversation. Check it out.

Ready to Submit a Package for Review?

To submit a package to us, you need to open an issue in our peer review GitHub repository. Learn about the steps to submit a package for open peer review in our guidebook.

Meet our editorial board

The pyOpenSci software peer review process is led by a volunteer team of editors from the scientific Python community. Editors do the following things:

  • They find reviewers from diverse backgrounds who have a mixture of scientific domain and Python experience.
  • They oversee the entire review process for a package ensuring it runs in a timely and efficient manner
  • They support the submitting authors and reviewers in answering questions related to the review
  • They determine whether that package should be accepted into the pyOpenSci ecosystem once the review has wrapped up.

Learn more about the editor role at pyOpenSci in our peer review guide.

GitHub photo of Filipe

Filipe

Advisory Council, Editor

GitHub photo of Eliot Robson

Eliot Robson

Peer Review Lead, Editor, Emeritus Editor in Chief

UIUC

GitHub photo of Lauren Yee

Lauren Yee

Editor, Editor in Chief

GitHub photo of David Nicholson

David Nicholson

Emeritus Editor in Chief, Editor

GitHub photo of Tom Russell

Tom Russell

Editor

University of Oxford

GitHub photo of C. Titus Brown

C. Titus Brown

Editor

University of California, Davis

GitHub photo of Hans Moritz Günther

Hans Moritz Günther

Astropy

Editor

MIT

GitHub photo of Derek Homeier

Derek Homeier

Astropy

Editor

GitHub photo of Tetsuo Koyama

Tetsuo Koyama

@ark-info-sys

GitHub photo of Avik Basu

Avik Basu

Editor

Intuit

GitHub photo of Jonas Eschle

Jonas Eschle

Editor

CERN


Emeritus & Guest Editors

We are deeply grateful for those served on our editorial board previously!

GitHub photo of Leah Wasser

Leah Wasser

Executive Director & Founder, Emeritus editor

pyOpenSci

GitHub photo of Ivan Ogasawara

Ivan Ogasawara

Advisory Council, Emeritus editor

xmnlab

GitHub photo of Ariane Sasso

Ariane Sasso

Emeritus Editor

@hpi-dhc

GitHub photo of Chiara Marmo

Chiara Marmo

Emeritus Editor in Chief, Emeritus Editor, Peer review triage

GitHub photo of Jenny Palomino

Jenny Palomino

Emeritus Editor

Google

GitHub photo of Anita Graser

Anita Graser

Emeritus Editor

GitHub photo of Alex Batisse

Alex Batisse

Emeritus Editor in Chief, EmeritusEditor

GitHub photo of Luiz Irber

Luiz Irber

Emeritus editor

GitHub photo of Ben Cook

Ben Cook

Guest editor

GitHub photo of Meenal Jhajharia

Meenal Jhajharia

Emeritus Editor

\varnothing

GitHub photo of Isabel Zimmerman

Isabel Zimmerman

Emeritus Editor in Chief, Emeritus Editor

@rstudio

GitHub photo of Nima Sarajpoor

Nima Sarajpoor

Emeritus Editor


Recently accepted Python packages

BlockingPy

Blocking records for record linkage and deduplication with Approximate Nearest Neighbor algorithms.;

swiftgalaxy

Load in particles of a simulated galaxy, rotate coordinates, easy spherical/cylindrical coordinates, access integrated properties, and more.

ChemInformant

A robust, high-throughput Python client for retrieving chemical information from the PubChem API; it returns analysis-ready Pandas/SQL outputs, handles caching, rate-limiting and retries, and includes convenient CLI tools.


View All Accepted Packages