Skip to content

Check ups

A check up is a single, named membership criterion of the Qiskit Ecosystem, such as "have a commit within the last 12 months" or "have an OSI-approved license". They are re-run on every member every week, so this page is the current state of the whole ecosystem: each check up, and the projects it is failing right now.

A failing check up is not a removal. It moves the project to Under revision and starts its cure period; only when that period runs out without the check up being fixed or explained does the project become Alumni. See how the check ups work for the mechanism, and for project maintainers if one of these is on your project.

All the check ups

Failing counts current members only. Alumni counts the projects that were retired with the check up recorded on them — for those, it is why they stopped being members.

Check up Applies to Category Importance Cure period Failing Alumni
[000] Build on, interface with, or extend Qiskit in a meaningful way all SUBMISSION CRITICAL 0 days 0 0
[001] Have an OSI-approved license all OSS CRITICAL 0 days 0 2
[004] Maturity property has to exist and be valid all SUBMISSION IMPORTANT 90 days 0 0
[007] Interfaces have to exist all SUBMISSION IMPORTANT 90 days 0 2
[008] Category has to exist all SUBMISSION IMPORTANT 90 days 0 0
[009] Labels have to exist all SUBMISSION IMPORTANT 90 days 0 0
[010] member.name should not include the substring 'test' all SUBMISSION RECOMMENDATION 180 days 0 0
[011] Do not repeat URLs in the submission all SUBMISSION STRONG-RECOMMENDATION 90 days 0 0
[012] URLs must exist all SUBMISSION IMPORTANT 90 days 0 0
[013] URLs use a secure scheme all SUBMISSION IMPORTANT 90 days 0 1
[014] Description too long all SUBMISSION IMPORTANT 90 days 0 0
[015] URL should not point to a GitHub organization all SUBMISSION IMPORTANT 90 days 0 0
[020] Primitive interface should be v2-compatible label:"Compute provider" OUT-OF-DATE CRITICAL 0 days 0 1
[025] Documentation link has redundant suffix all SUBMISSION RECOMMENDATION 180 days 0 0
[026] The /README.md file is not documentation all SUBMISSION RECOMMENDATION 180 days 0 0
[027] Website should not be GitHub repository or PyPI URL all SUBMISSION STRONG-RECOMMENDATION 90 days 0 2
[COC] Adhere to the Qiskit CoC all SUBMISSION CRITICAL 0 days 0 0
[G00] Have a clear support expectation and, if actively maintained, show signs of that activity. all GENERAL CRITICAL 0 days 0 26
[G05] Archived GitHub repository should be declared as-is GitHub projects ACTIVITY CRITICAL 0 days 0 16
[G06] Have maintainer activity within the last 6 months GitHub projects ACTIVITY RECOMMENDATION 180 days 3 5
[G07] Have a commit within the last 12 months GitHub projects ACTIVITY STRONG-RECOMMENDATION 90 days 4 16
[G08] Unmaintained projects should be archived in GitHub repository GitHub projects ACTIVITY NICE-TO-HAVE 270 days 5 0
[G09] GitHub is not detecting the repository license GitHub projects OSS RECOMMENDATION 180 days 1 2
[G10] The repository license is not (probably) OSI-approved GitHub projects OSS IMPORTANT 90 days 0 0
[G11] unmaintained projects should be archived when the repository is on an IBM-controlled organization GitHub projects ACTIVITY STRONG-RECOMMENDATION 90 days 0 0
[G12] Have a commit within the last (age * 2/3) months GitHub projects ACTIVITY IMPORTANT 60 days 5 1
[I00] IBM-maintained project not in an IBM-controlled GitHub organization IBM-maintained projects OSS CRITICAL 0 days 0 0
[J00] Julia package without license Julia packages OSS RECOMMENDATION 180 days 1 0
[J01] The license declared in Julia is (probably) not OSI-approved Julia packages OSS IMPORTANT 90 days 0 0
[O01] Have a license all OSS CRITICAL 0 days 0 0
[O02] member.license is not OSI-approved license all SUBMISSION IMPORTANT 90 days 0 2
[P00] Python package license-related metadata should refer to an OSI-approved license Python packages OSS CRITICAL 0 days 0 0
[P11] Production-ready projects should have, at least, one stable Python package Python packages OUT-OF-DATE STRONG-RECOMMENDATION 90 days 0 0
[P12] PyPI package without license Python packages OSS RECOMMENDATION 180 days 1 4
[P13] The license declared in PyPI is (probably) not OSI-approved Python packages OSS IMPORTANT 90 days 0 0
[PQ1] Be installable with qiskit>=1.0 Python packages OUT-OF-DATE LEGACY no deadline 0 0
[Q02] Be installable with qiskit>=2.0 projects that declare a qiskit dependency OUT-OF-DATE IMPORTANT 90 days 1 11
[Q03] Have a cap on the major version for the qiskit dependency projects that declare a qiskit dependency BEST-PRACTICE RECOMMENDATION 180 days 3 9
[Q04] Not depend on a pre-release of Qiskit projects that declare a qiskit dependency BEST-PRACTICE RECOMMENDATION 180 days 1 0
[Q20] Be compatible with the Qiskit SDK v2 or newer all GENERAL CRITICAL 0 days 0 11
[S00] The license declared in the repository is (probably) not OSI-approved pip-installable repositories OSS IMPORTANT 90 days 0 0

[000] Build on, interface with, or extend Qiskit in a meaningful way

CRITICAL · SUBMISSION · applies to all · cure period: 0 days

Software in the Qiskit Ecosystem should be related to Qiskit projects in some meaningful way. Software that manipulates Qiskit data structures (such as transpiler plugins) are good examples of that. If the connection with Qiskit is not that obvious, consider having a tutorial or how-to guide explaining a use-case for Qiskit users.

This check up is not a test: it is raised by hand, and tracked in the issue that the member file points to.

No project is failing this check up

[001] Have an OSI-approved license

CRITICAL · OSS · applies to all · cure period: 0 days

Projects in the Qiskit Ecosystem (and their packages) must have an OSI-approved license.

Checked by checkup_general.py::checkup_001.

No current member is failing this check up

2 Alumni projects also failed this check up

[004] Maturity property has to exist and be valid

IMPORTANT · SUBMISSION · applies to all · cure period: 90 days

member.maturity should exist in https://qiskit.github.io/ecosystem/classifications/#maturity

Checked by checkup_classifications.py::checkup_004.

No project is failing this check up

[007] Interfaces have to exist

IMPORTANT · SUBMISSION · applies to all · cure period: 90 days

All member.interfaces should exist in https://qiskit.github.io/ecosystem/classifications/#interfaces

Checked by checkup_classifications.py::checkup_007.

No current member is failing this check up

2 Alumni projects also failed this check up

[008] Category has to exist

IMPORTANT · SUBMISSION · applies to all · cure period: 90 days

member.category should exist in https://qiskit.github.io/ecosystem/classifications/#category

Checked by checkup_classifications.py::checkup_008.

No project is failing this check up

[009] Labels have to exist

IMPORTANT · SUBMISSION · applies to all · cure period: 90 days

All member.labels should exist in https://qiskit.github.io/ecosystem/classifications/#labels

Checked by checkup_classifications.py::checkup_009.

No project is failing this check up

[010] member.name should not include the substring 'test'

RECOMMENDATION · SUBMISSION · applies to all · cure period: 180 days

Projects in the Qiskit Ecosystem should be related

Checked by checkup_name.py::checkup_010.

No project is failing this check up

[011] Do not repeat URLs in the submission

STRONG-RECOMMENDATION · SUBMISSION · applies to all · cure period: 90 days

Having the same URL for, for example member.website and member.documentation is unnecessary. Keep the better fit and remove the other one.

This check up is not a test: it is raised by hand, and tracked in the issue that the member file points to.

No project is failing this check up

[012] URLs must exist

IMPORTANT · SUBMISSION · applies to all · cure period: 90 days

URLs must not return 404s or other forms of permanent errors. Redirects are accepted.

This check up is not a test: it is raised by hand, and tracked in the issue that the member file points to.

No project is failing this check up

[013] URLs use a secure scheme

IMPORTANT · SUBMISSION · applies to all · cure period: 90 days

All the URLs must use HTTPS (HyperText Transfer Protocol Secure) scheme.

Checked by checkup_url.py::CheckupURLs::checkup_013.

No current member is failing this check up

1 Alumni project also failed this check up

[014] Description too long

IMPORTANT · SUBMISSION · applies to all · cure period: 90 days

Member description cannot be longer than 135 characters because of front-end design limitations.

Checked by checkup_description.py::checkup_014.

No project is failing this check up

[015] URL should not point to a GitHub organization

IMPORTANT · SUBMISSION · applies to all · cure period: 90 days

The member.url field should not point to a GitHub organization page. It should link to the source code page, not the parent organization.

Checked by checkup_general.py::checkup_015.

No project is failing this check up

[020] Primitive interface should be v2-compatible

CRITICAL · OUT-OF-DATE · applies to label:"Compute provider" · cure period: 0 days

If the project implements a Qiskit primitive interface, it should be compatible with the V2 primitives API.

This check up is not a test: it is raised by hand, and tracked in the issue that the member file points to.

No current member is failing this check up

1 Alumni project also failed this check up

[025] Documentation link has redundant suffix

RECOMMENDATION · SUBMISSION · applies to all · cure period: 180 days

Links like https://qiskit-banana-compiler.readthedocs.io/en/latest/ do not need the /en/latest suffix.

Checked by checkup_url.py::CheckupURLs::checkup_025.

No project is failing this check up

[026] The /README.md file is not documentation

RECOMMENDATION · SUBMISSION · applies to all · cure period: 180 days

It is fine to leave the member.documentation field empty. Pointing to the README.md file is not necessary.

Checked by checkup_url.py::CheckupURLs::checkup_026.

No project is failing this check up

[027] Website should not be GitHub repository or PyPI URL

STRONG-RECOMMENDATION · SUBMISSION · applies to all · cure period: 90 days

The member.website field should point to the project's website instead of the GitHub repository or a PyPI project page.

Checked by checkup_url.py::CheckupURLs::checkup_027.

No current member is failing this check up

2 Alumni projects also failed this check up

[COC] Adhere to the Qiskit CoC

CRITICAL · SUBMISSION · applies to all · cure period: 0 days

Project submitters should adhere to the Qiskit code of conduct. If the submitter is the project maintainer, they can enforce their own code of conduct in addition to the one coming from Qiskit.

This check up is not a test: it is raised by hand, and tracked in the issue that the member file points to.

No project is failing this check up

[G00] Have a clear support expectation and, if actively maintained, show signs of that activity.

CRITICAL · GENERAL · applies to all · cure period: 0 days

Actively maintained projects should show signs of that. This includes recent activity in the code repository (such as commits, issue responses, or pull requests) as well as reasonably up-to-date package releases. Projects with no observable activity over an extended period may be considered abandoned.

Checked by checkup_general.py::checkup_G00.

No current member is failing this check up

26 Alumni projects also failed this check up

[G05] Archived GitHub repository should be declared as-is

CRITICAL · ACTIVITY · applies to GitHub projects · cure period: 0 days

An archived GitHub repository cannot be maintained anymore, so the project should declare member.maturity as as-is, the only maturity that states no active maintenance expectations. Every other maturity, deprecated included, is checked: a project that is still offered for use should not have its repository archived.

Checked by checkup_github.py::checkup_G05.

No current member is failing this check up

16 Alumni projects also failed this check up

[G06] Have maintainer activity within the last 6 months

RECOMMENDATION · ACTIVITY · applies to GitHub projects · cure period: 180 days

Projects available on GitHub should have some activity within the last 6 months, such as somebody starring the repository. The lack of this kind of activity might signal a dormant project. This check up does not apply to projects that declare no maintenance expectations (member.maturity is as-is or deprecated).

Checked by checkup_github.py::checkup_G06.

There are 3 projects failing this check up
Project Maturity Status Days left in the cure period
Quantum Network Coding production-ready Under revision 89
(Large-scale) Quantum Network Coding production-ready Under revision 89
Qiskit Nature PySCF production-ready Under revision 119
5 Alumni projects also failed this check up

[G07] Have a commit within the last 12 months

STRONG-RECOMMENDATION · ACTIVITY · applies to GitHub projects · cure period: 90 days

Projects available on GitHub should have commit activity within the last 12 months. The lack of this kind of activity might signal a dormant project. This check up does not apply to projects that declare no maintenance expectations (member.maturity is as-is or deprecated).

Checked by checkup_github.py::checkup_G07.

There are 4 projects failing this check up
Project Maturity Status Days left in the cure period
fast-pauli production-ready Under revision 64
FAdam-VQE production-ready Under revision 64
Qiskit Nature PySCF production-ready Under revision 64
symbolic-qiskit production-ready Under revision 64
16 Alumni projects also failed this check up
1 project with an explanation for this check up
Project Maturity Status Explanation Explanation expires in
BasisConstructor plugin for Qiskit transpiler experimental Member The project is maintained, it is just having a slow moment 79 days

[G08] Unmaintained projects should be archived in GitHub repository

NICE-TO-HAVE · ACTIVITY · applies to GitHub projects · cure period: 270 days

Projects that are not maintained (that is, member.maturity is as-is or deprecated) should archive their GitHub repositories to signal other users and developers that issues or PRs are not going to be addressed.

Checked by checkup_github.py::checkup_G08.

There are 5 projects failing this check up
Project Maturity Status Days left in the cure period
Qiskit Spacetime Bridge as-is Unmaintained 251
GALA-n Quantum Library as-is Unmaintained 251
Grover controlled-diffuser (CUs) as-is Unmaintained 251
CALA-n Quantum Library as-is Unmaintained 251
Qiskit Nature + CP2K Embedding as-is Unmaintained 251

[G09] GitHub is not detecting the repository license

RECOMMENDATION · OSS · applies to GitHub projects · cure period: 180 days

GitHub cannot detect the repository license

Checked by checkup_github.py::checkup_G09.

There is 1 project failing this check up
Project Maturity Status Days left in the cure period Discussion
QCRAFT AutoScheduler experimental Under revision 81 discussion
2 Alumni projects also failed this check up

[G10] The repository license is not (probably) OSI-approved

IMPORTANT · OSS · applies to GitHub projects · cure period: 90 days

GitHub detects a license for the repository, but its SPDX identifier is not one of the OSI-approved ones. This might be a sign that the project is not open source, or that the license is declared in a way that automatic detection cannot match. The case where GitHub detects no license at all is [G09] instead.

Checked by checkup_github.py::checkup_G10.

No project is failing this check up

[G11] unmaintained projects should be archived when the repository is on an IBM-controlled organization

STRONG-RECOMMENDATION · ACTIVITY · applies to GitHub projects · cure period: 90 days

Like [G08], projects that are not maintained (that is, member.maturity is as-is or deprecated) should archive their GitHub repositories. When the repository lives in a GitHub organization controlled by IBM, there is nothing standing in the way of doing it, so the recommendation is a stronger one.

Checked by checkup_github.py::checkup_G11.

No project is failing this check up

[G12] Have a commit within the last (age * 2/3) months

IMPORTANT · ACTIVITY · applies to GitHub projects · cure period: 60 days

Projects whose GitHub repository is less than 12 months old should have commit activity within the last two thirds of the age of that repository, and in any case within the last 2 months. A project that stops committing this early has little track record to fall back on. Older repositories are covered by the flat window of [G07] instead.

Checked by checkup_github.py::checkup_G12.

There are 5 projects failing this check up
Project Maturity Status Days left in the cure period
(Large-scale) Quantum Network Coding production-ready Under revision 41
HLQuantum production-ready Under revision 31
qvoting experimental Under revision 41
Quantum OpenQASM Assistant production-ready Under revision 43
qiskit-data-reuploading experimental Under revision 55
1 Alumni project also failed this check up

[I00] IBM-maintained project not in an IBM-controlled GitHub organization

CRITICAL · OSS · applies to IBM-maintained projects · cure period: 0 days

Projects that are maintained by IBM should live in a GitHub organization that is controlled by IBM. This allows, for example, projects to be archived once they are no longer maintained.

Checked by checkup_ibm_maintained.py::checkup_I00.

No project is failing this check up

[J00] Julia package without license

RECOMMENDATION · OSS · applies to Julia packages · cure period: 180 days

Every Julia package of the project should declare a license in its metadata. This is about what the package publishes: a repository can have a LICENSE file and still ship packages that declare nothing.

Checked by checkup_julia.py::checkup_J00.

There is 1 project failing this check up
Project Maturity Status Days left in the cure period
QiskitIBMRuntime.jl experimental Qiskit Project 84

[J01] The license declared in Julia is (probably) not OSI-approved

IMPORTANT · OSS · applies to Julia packages · cure period: 90 days

The license declared by every Julia package of the project should be an OSI-approved open-source license. The check up matches the declared license against the SPDX identifiers of the OSI-approved ones, so a license spelled in an unusual way can fail it without the project being any less open source. A package declaring no license at all is [J00] instead.

Checked by checkup_julia.py::checkup_J01.

No project is failing this check up

[O01] Have a license

CRITICAL · OSS · applies to all · cure period: 0 days

Projects must have a license, somewhere.

Checked by checkup_license.py::checkup_O01.

No project is failing this check up

[O02] member.license is not OSI-approved license

IMPORTANT · SUBMISSION · applies to all · cure period: 90 days

member.license could not be found among the OSI-approved licenses.

Checked by checkup_license.py::checkup_O02.

No current member is failing this check up

2 Alumni projects also failed this check up

[P00] Python package license-related metadata should refer to an OSI-approved license

CRITICAL · OSS · applies to Python packages · cure period: 0 days

The license-related metadata in PyPA should be an OSI-approved open-source license.

This check up is not a test: it is raised by hand, and tracked in the issue that the member file points to.

No project is failing this check up

[P11] Production-ready projects should have, at least, one stable Python package

STRONG-RECOMMENDATION · OUT-OF-DATE · applies to Python packages · cure period: 90 days

If the project maturity level is production-ready then, at least one of the Python packages should have a Development Status classifier that is None, Production/Stable, or Mature.

Checked by checkup_pypi.py::checkup_P11.

No project is failing this check up

[P12] PyPI package without license

RECOMMENDATION · OSS · applies to Python packages · cure period: 180 days

The Python package does not have a license declared in PyPI.

Checked by checkup_pypi.py::checkup_P12.

There is 1 project failing this check up
Project Maturity Status Days left in the cure period Discussion
Qiskit Quantum Backend Selector experimental Under revision 161 discussion
4 Alumni projects also failed this check up
8 projects with an explanation for this check up
Project Maturity Status Explanation Explanation expires in Discussion
Qamomile production-ready Member Issue asking for the license declaration submitted https://github.com/Jij-Inc/Qamomile/issues/655, waiting for a release with the fix 169 days discussion
fast-pauli production-ready Under revision Issue asking for the license declaration submitted https://github.com/qognitive/fast-pauli/issues/97, waiting for a release with the fix 169 days discussion
pytket-qiskit production-ready Member Issue asking for the license declaration submitted https://github.com/Quantinuum/pytket-qiskit/issues/555, waiting for a release with the fix 169 days discussion
Qclib production-ready Member Issue asking for the license declaration submitted https://github.com/qclib/qclib/issues/215, waiting for a release with the fix 169 days discussion
qiskit-gym experimental Member Issue asking for the license declaration submitted https://github.com/AI4quantum/qiskit-gym/issues/18, waiting for a release with the fix 169 days discussion
Dice eigensolver experimental Qiskit Project PR with fix was merged, but not yet released to PyPI 79 days discussion
Qiskit Omelyan bugfixing only Early Project Issue asking for the license declaration submitted https://github.com/MarkoMalezic/qiskit-omelyan/issues/2, waiting for a release with the fix 169 days discussion
Bosonic Qiskit production-ready Member The license declaration is already in the repository (https://github.com/C2QA/bosonic-qiskit/commit/b4fc994189d3b4772edc36405b45ae6970fa87f3), waiting for a release with the fix 48 days discussion

[P13] The license declared in PyPI is (probably) not OSI-approved

IMPORTANT · OSS · applies to Python packages · cure period: 90 days

The license declared in PyPI by every Python package of the project should be an OSI-approved open-source license. The check up matches the declared license against the SPDX identifiers of the OSI-approved ones, so a license spelled in an unusual way can fail it without the project being any less open source. A package declaring no license at all is [P12] instead.

Checked by checkup_pypi.py::checkup_P13.

No project is failing this check up

[PQ1] Be installable with qiskit>=1.0

LEGACY · OUT-OF-DATE · applies to Python packages · cure period: no deadline

Python packages that depend on Qiskit SDK, there should exist a supported release that is compatible with the Qiskit SDK v1.0 or newer.

Checked by checkup_pypi.py::checkup_PQ1.

No project is failing this check up

[Q02] Be installable with qiskit>=2.0

IMPORTANT · OUT-OF-DATE · applies to projects that declare a qiskit dependency · cure period: 90 days

If the project depends on Qiskit SDK, what it requires should allow v2.0 or newer. This is asked of every place a project can declare its qiskit dependency: a published distribution, a packaging manifest in the repository, and a requirements file. A project can be compatible in its latest release and not in its source, which is what anybody installing from the repository gets, so each one is read on its own. It replaces [PQ2], [S01] and [R01], one per section, which were the same question asked three times.

Checked by checkup_general.py::checkup_Q02.

There is 1 project failing this check up
Project Maturity Status Days left in the cure period
Qiskit Installer for Windows production-ready Under revision 82
11 Alumni projects also failed this check up
1 project with an explanation for this check up
Project Maturity Status Explanation Explanation expires in Discussion
Qutes Programming Language production-ready Member Issue asking for Qiskit v2 support submitted https://github.com/GabrieleMessina/qutes_lang/issues/99, waiting for the fix 48 days discussion

[Q03] Have a cap on the major version for the qiskit dependency

RECOMMENDATION · BEST-PRACTICE · applies to projects that declare a qiskit dependency · cure period: 180 days

As Qiskit follows semantic versioning, a dependency with no cap for the eventual next major version gives no guarantee that the project will keep working after a major release. This is asked of every place a project can declare its qiskit dependency: a published distribution, a packaging manifest in the repository, and a requirements file. It replaces [P10], [S02] and [R02], one per section, which were the same question asked three times.

Checked by checkup_general.py::checkup_Q03.

There are 3 projects failing this check up
Project Maturity Status Days left in the cure period
Quantum Network Coding production-ready Under revision 172
(Large-scale) Quantum Network Coding production-ready Under revision 172
QRMI (Quantum resource management interface) experimental Under revision 172
9 Alumni projects also failed this check up
64 projects with an explanation for this check up
Project Maturity Status Explanation Explanation expires in Discussion
ffsim production-ready Member Issue asking for the cap submitted https://github.com/qiskit-community/ffsim/issues/712, waiting for a release with the fix 169 days discussion
Qiskit Finance production-ready Member Issue asking for the cap submitted https://github.com/qiskit-community/qiskit-finance/issues/363, waiting for a release with the fix 169 days discussion
truncated Variational Hamiltonian Ansatz tVHA production-ready Member Issue asking for the cap submitted https://github.com/clemens-sauer-possel/tvha/issues/3, waiting for the fix 169 days discussion
MQT Core production-ready Member Issue asking for the cap submitted https://github.com/munich-quantum-toolkit/core/issues/2622, waiting for a release with the fix 169 days discussion
MQT DDSIM production-ready Member Issue asking for the cap submitted https://github.com/munich-quantum-toolkit/ddsim/issues/1017, waiting for a release with the fix 169 days discussion
qiskit-trev experimental Early Project Issue asking for the cap submitted https://github.com/keunjunpark/qiskit-trev/issues/7, waiting for a release with the fix 169 days discussion
BasisConstructor plugin for Qiskit transpiler experimental Member Issue asking for the cap submitted https://github.com/qiskit-community/qiskit-basis-constructor/issues/9, waiting for a release with the fix 169 days discussion
quantum-learn experimental Member Issue asking for the cap submitted https://github.com/KUQCI/quantum-learn/issues/10, waiting for a release with the fix 169 days discussion
Qamomile production-ready Member Issue asking for the cap submitted https://github.com/Jij-Inc/Qamomile/issues/653, waiting for a release with the fix 169 days discussion
Aer bugfixing only Qiskit Project PR with a fix submitted https://github.com/Qiskit/qiskit-aer/pull/2461, waiting for merge and release 109 days discussion
MQT QECC production-ready Member Issue asking for the cap submitted https://github.com/munich-quantum-toolkit/qecc/issues/836, waiting for a release with the fix 169 days discussion
Best practices in quantum optimization with Qiskit experimental Member Issue asking for the cap submitted https://github.com/qiskit-community/qopt-best-practices/issues/66, waiting for the fix 169 days discussion
Qiskit Quantum Machines Provider production-ready Member Issue asking for the cap submitted https://github.com/arthurostrauss/qiskit-qm-provider/issues/12, waiting for a release with the fix 169 days discussion
Samplomatic experimental Qiskit Project Issue asking for the cap submitted https://github.com/Qiskit/samplomatic/issues/413, waiting for a release with the fix 169 days discussion
QuPepFold production-ready Member Issue asking for the cap submitted https://github.com/akshayuttarkarc/QuPepFold/issues/8, waiting for a release with the fix 169 days discussion
QuPrep experimental Early Project Issue asking for the cap submitted https://github.com/quprep/quprep/issues/42, waiting for a release with the fix 169 days discussion
Noisy Quantum Gates production-ready Member Issue asking for the cap submitted https://github.com/CERN-QTI/quantum-gates/issues/62, waiting for a release with the fix 169 days discussion
Qiskit Experiments production-ready Member Issue asking for the cap submitted https://github.com/qiskit-community/qiskit-experiments/issues/1656, waiting for a release with the fix 169 days discussion
Qiskit Rigetti Provider experimental Alumni The cap is already in the repository (https://github.com/rigetti/qiskit-rigetti/pull/55, July 2024), but there has been no release since February 2024 110 days discussion
QSP-SQD experimental Member Issue asking for the cap submitted https://github.com/JoelHBierman/QSP-SQD/issues/1, waiting for the fix 169 days discussion
Qiskit C++ experimental Qiskit Project Issue asking for the cap submitted https://github.com/Qiskit/qiskit-cpp/issues/167, waiting for the fix 169 days discussion
fast-pauli production-ready Under revision Issue asking for the cap submitted https://github.com/qognitive/fast-pauli/issues/98, waiting for a release with the fix 169 days discussion
quPython bugfixing only Member Issue asking for the cap submitted https://github.com/frankharkins/quPython/issues/1, waiting for a release with the fix 169 days discussion
HLQuantum production-ready Under revision Issue asking for the cap submitted https://github.com/AlinDanielFerenczi/HLQuantum/issues/1, waiting for a release with the fix 169 days discussion
quantum-chemistry-vqe experimental Early Project Issue asking for the cap submitted https://github.com/Venkatallu11/quantum-chemistry-vqe/issues/1, waiting for the fix 169 days discussion
MQT Bench experimental Member Issue asking for the cap submitted https://github.com/munich-quantum-toolkit/bench/issues/1035, waiting for a release with the fix 169 days discussion
pytket-qiskit production-ready Member Issue asking for the cap submitted https://github.com/Quantinuum/pytket-qiskit/issues/552, waiting for a release with the fix 169 days discussion
arvak-lite experimental Early Project Issue asking for the cap submitted https://github.com/hiq-lab/arvak-lite/issues/2, waiting for a release with the fix 169 days discussion
Importer from OpenQASM 3 to Qiskit experimental Qiskit Project Issue asking for the cap submitted https://github.com/Qiskit/qiskit-qasm3-import/issues/68, waiting for a release with the fix 169 days discussion
Qiskit QKD Lab experimental Very Early Project Issue asking for the cap submitted https://github.com/RexRowan/Qiskit-QKD-Lab/issues/1, waiting for a release with the fix 169 days discussion
MQT ProblemSolver experimental Member Issue asking for the cap submitted https://github.com/munich-quantum-toolkit/problemsolver/issues/560, waiting for a release with the fix 169 days discussion
GALA-n Quantum Library as-is Unmaintained Check-up was introduced after the project was set as unmaintained. never
Qiskit IonQ Provider production-ready Member Issue asking for the cap submitted https://github.com/qiskit-community/qiskit-ionq/issues/274, waiting for a release with the fix 169 days discussion
Qiberis experimental Very Early Project Issue asking for the cap submitted https://github.com/RexRowan/Qiberis/issues/1, waiting for a release with the fix 169 days discussion
Qiskit Qulacs production-ready Member Issue asking for the cap submitted https://github.com/Gopal-Dahale/qiskit-qulacs/issues/11, waiting for a release with the fix 169 days discussion
qvoting experimental Under revision Issue asking for the cap submitted https://github.com/cogu92/qvoting/issues/1, waiting for a release with the fix 169 days discussion
Qclib production-ready Member Issue asking for the cap submitted https://github.com/qclib/qclib/issues/214, waiting for a release with the fix 169 days discussion
Grover controlled-diffuser (CUs) as-is Unmaintained Check-up was introduced after the project was set as unmaintained. never
qiskit-gym experimental Member Issue asking for the cap submitted https://github.com/AI4quantum/qiskit-gym/issues/17, waiting for a release with the fix 169 days discussion
qiskit-noise-learning experimental Qiskit Project Issue asking for the cap submitted https://github.com/Qiskit/qiskit-noise-learning/issues/146, waiting for the fix 169 days discussion
Benchpress experimental Qiskit Project Issue asking for the cap submitted https://github.com/Qiskit/benchpress/issues/116, waiting for the fix 169 days discussion
Qiskit Algorithms production-ready Member PR with a fix submitted, waiting for merge 78 days discussion
Quantum Fragment Methods experimental Early Project Issue asking for the cap submitted https://github.com/qiskit-community/quantum-fragment-methods/issues/13, waiting for the fix 48 days discussion
piQture production-ready Member Issue asking for the cap submitted https://github.com/SaashaJoshi/piQture/issues/176, waiting for a release with the fix 169 days discussion
MQT QMAP production-ready Member Issue asking for the cap submitted https://github.com/munich-quantum-toolkit/qmap/issues/1174, waiting for a release with the fix 169 days discussion
qiskit-symb production-ready Member Issue asking for the cap submitted https://github.com/SimoneGasperini/qiskit-symb/issues/11, waiting for a release with the fix 79 days discussion
M3 experimental Qiskit Project Issue asking for the cap submitted https://github.com/Qiskit/qiskit-addon-mthree/issues/287, waiting for a release with the fix 169 days discussion
Qiskit LEAN bridge experimental Very Early Project Issue asking for the cap submitted https://github.com/RexRowan/Qiskit-LEAN-Bridge/issues/1, waiting for the fix 48 days discussion
Qiskit Machine Learning production-ready Member Issue asking for the cap submitted https://github.com/qiskit-community/qiskit-machine-learning/issues/1072, waiting for a release with the fix 169 days discussion
PurpleCaffeine production-ready Member Issue asking for the cap submitted https://github.com/IceKhan13/purplecaffeine/issues/174, waiting for a release with the fix 169 days discussion
QASM Runner for IBM platforms production-ready Member Issue asking for the cap submitted https://github.com/TownsendBrown/QASM-Runner-for-IBM-platforms/issues/2, waiting for the fix 169 days discussion
Device Benchmarking experimental Member Issue asking for the cap submitted https://github.com/qiskit-community/qiskit-device-benchmarking/issues/87, waiting for the fix 169 days discussion
qiskit-qubit-reuse production-ready Member Issue asking for the cap submitted https://github.com/qiskit-community/qiskit-qubit-reuse/issues/19, waiting for a release with the fix 169 days discussion
Qiskit Graph Walks experimental Very Early Project The cap is already in the repository (https://github.com/RexRowan/Qiskit-Graph-Walks/commit/4c5f72cd7d63748f8c36f4314fd44e7dcbd022a9), waiting for a release with the fix 110 days discussion
CALA-n Quantum Library as-is Unmaintained Check-up was introduced after the project was set as unmaintained. never
qiskit-data-reuploading experimental Under revision Issue asking for the cap submitted https://github.com/Carlosandp/qiskit-data-reuploading/issues/4, waiting for a release with the fix 169 days discussion
Qiskit MCP Servers experimental Qiskit Project Issue asking for the cap submitted https://github.com/Qiskit/mcp-servers/issues/221, waiting for a release with the fix 169 days discussion
Qiskit StateViz experimental Very Early Project Issue asking for the cap submitted https://github.com/RexRowan/Qiskit-StateViz/issues/2, waiting for a release with the fix 169 days discussion
Qiskit Omelyan bugfixing only Early Project Issue asking for the cap submitted https://github.com/MarkoMalezic/qiskit-omelyan/issues/1, waiting for a release with the fix 169 days discussion
MQT Predictor experimental Member Issue asking for the cap submitted https://github.com/munich-quantum-toolkit/predictor/issues/832, waiting for a release with the fix 169 days discussion
qiskit-quimb production-ready Member The cap is already in the repository (https://github.com/qiskit-community/qiskit-quimb/pull/35), waiting for a release with the fix 110 days discussion
QAOA Training Pipeline experimental Member Issue asking for the cap submitted https://github.com/qiskit-community/qaoa_training_pipeline/issues/91, waiting for the fix 169 days discussion
Prefect Qiskit Plugin experimental Member Issue asking for the cap submitted https://github.com/qiskit-community/prefect-qiskit/issues/14, waiting for a release with the fix 169 days discussion
symbolic-qiskit production-ready Under revision Issue asking for the cap submitted https://github.com/ianchung621/symbolic-qiskit/issues/1, waiting for a release with the fix 169 days discussion

[Q04] Not depend on a pre-release of Qiskit

RECOMMENDATION · BEST-PRACTICE · applies to projects that declare a qiskit dependency · cure period: 180 days

A qiskit dependency should be written against released stable versions. A specifier that names a pre-release, like qiskit>=1.3.0rc1, enables pre-releases for that dependency: an installation gets the next release candidate as soon as it is published, which is a Qiskit nobody has tested the project against, and a release candidate becomes what the project reports as the highest Qiskit it supports. Depending on a release candidate is a reasonable thing to do while it is the only version with the feature the project needs; once the final version is out, the specifier should point at it.

Checked by checkup_general.py::checkup_Q04.

There is 1 project failing this check up
Project Maturity Status Days left in the cure period Discussion
Benchpress experimental Qiskit Project 172 discussion

[Q20] Be compatible with the Qiskit SDK v2 or newer

CRITICAL · GENERAL · applies to all · cure period: 0 days

If the software depends on Qiskit SDK in some way, there should exist a supported release that is compatible with the Qiskit SDK v2.0 or newer. This applies to Python packages and to other forms of dependencies. A project that publishes no release answers this with the distribution its repository declares or with its requirements file; [Q02] reads all three.

Checked by checkup_general.py::checkup_Q20.

No current member is failing this check up

11 Alumni projects also failed this check up

[S00] The license declared in the repository is (probably) not OSI-approved

IMPORTANT · OSS · applies to pip-installable repositories · cure period: 90 days

The license every distribution declares in its packaging manifests should be an OSI-approved open-source license. The check up matches the declared license against the SPDX identifiers of the OSI-approved ones, so a license spelled in an unusual way can fail it without the project being any less open source. A distribution that declares no license is not a check up here: the repository is what gets installed, and [G09] already asks the repository for one.

Checked by checkup_python.py::checkup_S00.

No project is failing this check up