Currently there is no way reliable to state that software is end of life/deprecated or other guidance. It's just information on websites that can't be easily accessed.
While Maven/npm/PyPI etc is one place to try to resolve this, another is GitHub Releases.
When releasing, a project can provide guidance of Pre-Release. It would be excellent if there were more options of guidance available, and that these are then edited over time by the project. The top example being End of Life, aka Do Not Use, aka Not Supported.
If this were added to the Releases page and API, I think it would provide a foundation for projects managing their version guidance more methodically.
Currently there is no way reliable to state that software is end of life/deprecated or other guidance. It's just information on websites that can't be easily accessed.
While Maven/npm/PyPI etc is one place to try to resolve this, another is GitHub Releases.
When releasing, a project can provide guidance of Pre-Release. It would be excellent if there were more options of guidance available, and that these are then edited over time by the project. The top example being End of Life, aka Do Not Use, aka Not Supported.
If this were added to the Releases page and API, I think it would provide a foundation for projects managing their version guidance more methodically.