A typical Rails app runs on Rails 7.2, Ruby 3.2, and PostgreSQL 15. It works fine. No one checks the support timelines. Then one day, Ruby 3.2 hits EOL and stops receiving security patches. Your stack is now technically unsupported, but upgrading these big dependencies takes months of planning and coordination. This is just a small example; imagine a company with many apps using different tech stacks, whether it's for a commercial project or a personal pet project.
The problem: tools like npm outdated or Dependabot catch small dependency updates. But the major dependencies (language, framework, database, OS) are different. They need advance warning so product owners can plan, teams can coordinate, and engineers can schedule the work.
I built Stack To Date to fill that gap.
What it does:
- Register your tech stack (manually or with the cli)
- Get a timeline showing when each dependency reaches EOL
- See support windows at a glance
- Share your stack status with a badge (for READMEs, dashboards, anywhere)
- Use the CLI to integrate into your workflow or CI/CD
It's all free, only a small signup form, not even confirmation for now.
The hard part is the data source provided by endoflife.date, so coverage includes major languages, frameworks, databases, and operating systems.
The codebase is built with Rails 8, modern tooling, and runs on Fly.io, The cli is go lang with the help of Claude.
I'd love your feedback. Let me know what you think.
0 comments
—
Show HN: Monitor when your tech stack goes EOL · HackerTrans
The problem: tools like npm outdated or Dependabot catch small dependency updates. But the major dependencies (language, framework, database, OS) are different. They need advance warning so product owners can plan, teams can coordinate, and engineers can schedule the work.
I built Stack To Date to fill that gap.
The hard part is the data source provided by endoflife.date, so coverage includes major languages, frameworks, databases, and operating systems.
The codebase is built with Rails 8, modern tooling, and runs on Fly.io, The cli is go lang with the help of Claude.
I'd love your feedback. Let me know what you think.