Some modules not listed?

Hm. So, you're saying that you have Features <1.3 installed and after installing the 'mydropwizard' module and visiting the "Available updates" report you're not being told that version 1.4 is available and a security update?

Enabling 'mydropwizard' is supposed to disable the core 'update' module, is it possible that 'update' is still enabled? I could see that maybe "covering up" the page provided by 'mydropwizard.

So, Features is not on the "Available updates" report at all? Or it is, there but the security update isn't being shown?

Hm! Is your copy of Features missing the project = "features" that's added by the Drupal.org packager? Although, I think it should try to default to the module name if it's missing...

Not sure if this should matter, but it's meant to be "features" with a lower-case "f". Maybe try that and see if it helps?

The Drupal.org packager should have put it's info below that, which means you might have gotten that module out of Git?

Ah, yeah, the missing version number could matter too... Sorry, I don't have time to actually experiment right now, but when I get a chance later, I'll try using that .info file locally and walk through the code!

We've encountered the same problem for all modules which have been fixed on our D6 sites. Has there been made any progress on this?

@LaravZ: Can you share the .info file for one of the modules that's enabled at an older version, but isn't showing up on the "Available updates" report? That was more or less where debugging with @davidneedham had left off. Another thing worth double checking is if the 'update' module is really disabled.

The features module is an example:
features.info

name = "Features"
description = "Provides feature management for Drupal."
core = 6.x
package = "Features"

There is no version, datestamp, or project defined. Which are present in other non-updated modules.

I finally got down to the bottom of this. It turns out that the core 'update' module also ignores the Features 6.x-1.x-dev module! So, it wasn't something wrong going on with our update status data end-point, which was where I thought this was going.

Here's a patch that will attempt to guess the project name if it isn't given. This could make for a messier update status report, or even Drupal claiming that custom modules are outdated versions of contrib modules, but I think that's better than missing possible security updates!

I've done some testing of this with Drush (to make sure this doesn't break any of our automation) and the change appears to have no effect, which is great! Drush appears to already have been guessing the project name somehow, because drush ups was already showing 'features' in my testing. So, as far as I can tell, the just affects the UI.

Committed!

Great, thanks!