At Phase2, as we develop more and more Drupal Platforms (more on this another time) we wind up with many custom modules that are not contributed back to drupal.org. They are either too tied to a specific client, or something that is not ready for general consumption, or frankly, the client might see as a strategic competitive advantage. Regardless of the reason, for modules not hosted on drupal.org you lose some ability to have the wonderful update_status module provide info to your site implementations when the custom modules are out of date….or so I thought.
