The time people will really start caring is in ten years time when the activiation servers are switched off and they can't play their games anymore.
Optimist. Microsoft "PlaysForSure" lasted for all of four years.
By the treating Open Source in the same way as commercial software we only start registering risks when there is an official announcement. We have no metric we can use to accurately gauge the state of an Open Source component, but there are a number of components that we have a "bad feeling" about.
Are there any standard ways of assessing the status of an open source project? Do you use the same stages for Open source as commercial components? How do you incorporate these in a software landscape to indicate at-risk components and dependencies?
Thus spake the master programmer: "After three days without programming, life becomes meaningless." -- Geoffrey James, "The Tao of Programming"