Software maturity refers to the stages a software project goes through during its lifecycle. While ECMWF runs operational services, this does not necessarily mean that the underlying software is operationally supported for external users. The following maturity levels provide an indication of how well-supported and operationally ready ECMWF software is. However, as with any open-source software, users should evaluate its suitability for their needs and use it at their own risk.
Graduated projects are ready for operations, and typically used by ECMWF and/or its Member and Cooperating states in operations. This does not mean ECMWF gives operational support to the software itself.
[](https://github.com/ecmwf/codex/raw/refs/heads/main/Project%20Maturity)
Incubating projects are mostly feature-complete and the interface is mostly stable. If this software is to be used in operational systems you are strongly advised to use a released tag in your system configuration, and you should be willing to accept incoming changes and bug fixes that require adaptations on your part. ECMWF may be using this software in operations and abides by the same caveats.
[](https://github.com/ecmwf/codex/raw/refs/heads/main/Project%20Maturity)
Emerging projects are in the early stages of development. There is a clear project goal, but they are not yet feature-complete and not stable.
[](https://github.com/ecmwf/codex/raw/refs/heads/main/Project%20Maturity)
Sandbox projects are experimental, proof-of-concept. Expect frequent changes, incomplete features and instability.
[](https://github.com/ecmwf/codex/raw/refs/heads/main/Project%20Maturity)
Projects that have reached the end of their lifecycle. They are no longer actively maintained or developed. These projects may still be available for reference or historical purposes, but they should not be used for any active development or operational purposes.
[](https://github.com/ecmwf/codex/raw/refs/heads/main/Project%20Maturity)