Puppetfile update follow transferred ownership in forge?

[freiheit]

It would be great if a puppetfile update noticed that a module was deprecated and tried to follow to the recommended alternative, especially if the alternative has the same last part. I see this when modules move into Vox Pupuli (puppet) most often, but could easily be other reasons for an "ownership" change of a module.

Example: https://forge.puppet.com/stahnma/epel moved to https://forge.puppet.com/puppet/epel -- but onceover update puppetfile suggests updating mod 'stahnma/epel', '1.3.1' to mod 'stahnma/epel', '2.0.0' instead of mod 'puppet/epel', '3.0.0'.