Skip to content

Maturity

Qiskit Ecosystem members have to be explicit on their support expectations, as well as their stability.

In same cases, the support level was infiered from the source code repository activity, like in archived.

Short descriptions
Maturity level Short description
as-is The project has no active maintenance expectations.
bugfixing only The project is minimally maintained. Bugs are fixed and dependencies are kept up to date, but no new features are planned.
deprecated The project still functional but no longer recommended for use.
experimental The project is under active development and breaking changes may be introduced at any point. Use in production with caution.
production-ready The project is mature, actively maintained, and stable. Recommended for production.
unmaintained The project is no longer maintained or supported.

as-is

There are 1 projects with this classification

When a project is released as-is, no active maintenance, bug fixes, or dependency updates are planned. It may work out of the box with the dependency versions available at the time of release, but compatibility with future versions is not guaranteed. Issues and pull requests may not be addressed. Typically, this applies to code published alongside a research paper, representing the state of the codebase at the time of publication for reproducibility purposes.

bugfixing only

There are 3 projects with this classification

Minimally maintained projects means that the lights are kept on to ensure continued functionality: bug fixes and dependency updates are applied as needed. However, no new features or significant improvements are planned or prioritized.

deprecated

No project with this classification

Deprecated projects are still functional but no longer recommended for use, typically because they have been superseded by a newer project or alternative. Usually, a grace period is provided to allow migration to the recommended replacement. During that period, minimal maintenance (such critical bug fixing) is expected, but no long-term support is planned.

experimental

There are 48 projects with this classification

An experimental project is under active development, with APIs and interfaces subject to breaking changes at any point without prior notice. They are not recommended for production use unless you are prepared to adapt to frequent updates.

production-ready

There are 88 projects with this classification

The project is mature, actively maintained, and stable. Recommended for production.

unmaintained

There are 9 projects with this classification

The project is no longer maintained or supported.