Package Submission

This page gives an overview of the submission process along with key principles to follow. See also Package Guidelines for package specific guidelines and requirement and the Bioconductor new package submission tracker.


To submit a package to Bioconductor the package should:

[ Back to top ]

Types of Packages

Bioconductor packages are broadly defined by three main package types: Software, Experiment Data, and Annotation.

See Package Guidelines for details on package format and syntax.

[ Back to top ]

Package Naming Policy

Package naming: i) Ownership of package name. Bioconductor follows CRAN’s policy in requiring that contributors give the right to use the package name to Bioconductor at time of submission, so that the Bioconductor team can orphan the package and allow another maintainer to take it over in the event that the package contributor discontinues package maintenance. See Bioconductor’s package end-of-life policy for more details. ii) Uniqueness of package name. Packages should be named in a way that does not conflict (irrespective of case) with any current or past BIOCONDUCTOR package, nor any current CRAN package.

[ Back to top ]

Author / Maintainer Expectations

Acceptance of packages into Bioconductor brings with it ongoing package maintenance responsibilities. Package authors are expected to:

[ Back to top ]


[ Back to top ]

Experiment Data Packages

Experimental data packages contain data specific to a particular analysis or experiment. They often accompany a software package for use in the examples and vignettes and in general are not updated regularly. If you need a general subset of data for workflows or examples first check the AnnotationHub resource for available files (e.g., BAM, FASTA, BigWig, etc.) or ExperimentHub for available processed example data set already included in Bioconductor. If no current files or data sets are appropriate consider an associated Experiment Data Package that utilizes ExperimentHub.

If you have an associated data package for your software package, please do NOT create a separate issue in the our tracker repository for that. Instead, please add the data package repository to the same issue as the software package. The process for doing this is documented here.

[ Back to top ]

Annotation Packages

Annotation packages contain lightly or non-curated data from a public source and are updated with each Bioconductor release (every 6 months). They are a source of general annotation for one or many organisms and are not specific to a particular experiment. When possible, they should support the select() interface from AnnotationDbi.

Annotation packages should NOT be posted to the tracker repository. Instead send an email to with a description of the proposed annotation package and futher instructions of where to send the package will be provided. Whenever possible Annotation Packages should use the AnnotationHub for managing files.

[ Back to top ]

Review Process

[ Back to top ]

Following Acceptance

Following acceptance of a package:

[ Back to top ]

Additional Support

We are eager to enhance the quality and interoperability of Bioconductor software and will provide additional support when requested by package developers. Example areas of assistance include use of appropriate S4 structures, specific guidance on efficient implementation, guidance on code structure, and critical assessment of package documentation and structure. Use the bioc-devel mailing list or email to obtain additional support.

[ Back to top ]

Source Code & Build Reports »

Source code is stored in Git.

Software packages are built and checked nightly. Build reports:


Development Version »

Bioconductor packages under development:

Developer Resources: