[Security/Compliance]: Formal archival request to assist enterprise migration efforts #17282
Replies: 1 comment
|
CRA was officially deprecated in February 2025, with its last release (v5.0.1) dating back to April 2022. React 19 has been stable since December 2024, and the official React documentation now directs developers to Vite, Next.js, and other modern tooling. Formally archiving the repository would:
Archiving would have zero practical impact on existing users while providing meaningful clarity for the ecosystem. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Description
As Create React App is no longer actively maintained and the official React documentation now strongly recommends modern bundlers like Vite or Next.js, many teams are currently in the process of migrating their legacy codebases.
However, because this repository is still technically open and not formally "archived" on GitHub, many strict enterprise compliance scanners do not flag the underlying deprecated dependencies (such as older
webpack-dev-serverversions with known prototype pollution warnings) as belonging to an End-of-Life (EOL) tool.Request
Could the maintainer team consider formally archiving this repository?
Archiving the repo would immediately signal to enterprise compliance tools that the project is officially EOL. This provides senior engineers with the necessary official documentation to justify the time and resources required for a Vite/Next.js migration to their management and security compliance boards.
Thank you for all the incredible work on this project over the years—it shaped the modern web, and an official archival would be a great final sign-off to help enterprise teams safely move forward.
All reactions