An OSS-cautious adopter and a CTO both wanted "will this be alive in 2 years" signals the page doesn't give:
- No per-project version, GitHub stars, release cadence, or named maintainers.
- No support model, Pro cost, or continuity story before asking for a roadmap-level bet.
Fix: add a compact per-project maturity strip (latest version + stars + "maintained since YYYY"), and a short "Support & Pro" band (support model + who's behind it). Surface the Shakapacker-succeeds-Webpacker lineage with dates - it's a strong longevity signal.
An OSS-cautious adopter and a CTO both wanted "will this be alive in 2 years" signals the page doesn't give:
Fix: add a compact per-project maturity strip (latest version + stars + "maintained since YYYY"), and a short "Support & Pro" band (support model + who's behind it). Surface the Shakapacker-succeeds-Webpacker lineage with dates - it's a strong longevity signal.