react/create-react-appcra_stale_stability_signal_probe_v1Can a highly familiar public repo still carry stale stability signals after its ecosystem moves on?
Type: controlled public repository and documentation example
Repo: react/create-react-app
react/create-react-appFoldEngine frames a technical claim or repository question, checks only the approved evidence surface, preserves what was and was not checked, and recommends one stabilizing next move.
Create React App looked stable through large visible adoption, years of tutorials, a simple beginner command, and ecosystem familiarity. React's February 2025 guidance changed the current interpretation: CRA is deprecated for new apps, and teams are pointed toward frameworks or modern build tools.
The public repository still carries high familiarity signals, including large star and fork counts. Those signals explain why CRA can still look stable at first glance, but they do not by themselves prove present support for new production work.
React's public post Sunsetting Create React App, published February 14, 2025.
Public GitHub repository surface for facebook/create-react-app, including visible popularity and issue activity signals.
React 19 compatibility discussion in issue #17004.
Documentation drift discussion in issue #13072, after CRA disappeared from the newer React docs path while older tutorials still referenced it.
The visible stability signal is stale rather than absent. CRA still has public familiarity, but the recommended path for new React applications moved to frameworks or build tools that handle production needs CRA did not fully close.
Signal class: false closure, stale trust signal, documentation drift, missing active maintainer anchor, projection-local stability, and migration seam.
Production needs named by the React guidance include routing, data fetching, code splitting, error handling, caching, navigation, and optimistic updates. The probe treats those as evidence that "easy app setup" was not the same as present production readiness.
Hygiene signal: the project can remain useful as maintenance-mode compatibility while no longer being the recommended starting point for new production apps.
Alignment signal: README, tutorial, and internal platform references should be checked for outdated "start here" language.
False closure: a problem appears solved because a familiar tool exists, while the surrounding production requirements are still open.
Stale trust signal: an old popularity or tutorial signal remains visible after the current recommended path changes.
Migration seam: the decision point where teams need to classify their app and choose whether to preserve, replace, or migrate the old starting point.
Documentation drift is visible because older tutorial memory and repo familiarity can keep pointing teams toward CRA even after React's current docs and blog guidance changed.
Primary insight: popularity and familiarity are useful evidence, but they must be checked against present maintainer support, current framework guidance, and the production needs the tool actually covers.
Recommended next move: Create a migration decision receipt: classify app type, recommend framework or build-tool path, identify blockers, add README-level migration warning where needed, and preserve CRA only as maintenance-mode compatibility.
Narrow task: pass - public sample is restricted to named public evidence.
Explicit envelope: pass - evidence and limits are listed.
Grounded insights only: pass - the report does not claim CRA is unusable, wrong, or blameworthy.
Classify the app as learning, static SPA, or production app; recommend a framework or build-tool path; identify blockers; and add a clear deprecation or migration note where the old CRA path still appears.
Generated at: 2026-05-17T00:00:00Z
Artifact version: trial_public_findings_report_v0_1
Intended vault: FoldEngine Operations / 03_Client_Reports / Public_Samples
Public sample URL: publication is allowed only for public_sample artifacts. Private/client reports must be retained without public exposure.