1. Could not hash remote project: [Name] 2. Could not hash remote project: [Name] 3. Could not hash local project [Name]

Strange, is this reproducible at all?

To me this happened when sharing the same temp-dir between a drupal6 and drupal7 installation. Problem resolved when using separate directories.

I'm having similar errors using the module with drush:
When I try to verify Drupal core with drush hd drupal I get:

WD hacked: Could not download the project: Drupal core from URL: http://ftp.drupal.org/files/projects/drupal-7.15.tar.gz         [error]
WD hacked: Could not download project: Drupal core                                                                               [error]
WD hacked: Could not hash remote project: Drupal core                                                                            [error]
WD hacked: Could not download the project: Drupal core from URL: http://ftp.drupal.org/files/projects/drupal-7.15.tar.gz         [error]
WD hacked: Could not download project: Drupal core                                                                               [error]
WD hacked: Could not hash remote project: Drupal core                                                                            [error]
WD hacked: Could not hash local project: Drupal core                                                                             [error]
Details for project: Drupal core
Total files: 0, files changed: 0, deleted files: 0

Detailed results:
 Status  File

HTTP error -1 occurred when trying to fetch http://ftp.drupal.org/files/projects/drupal-7.15.tar.gz.
HTTP error -1 occurred when trying to fetch http://ftp.drupal.org/files/projects/drupal-7.15.tar.gz.

Some with other modules as admin_menu, seems to work fine.

Generating the report in the UI shows a similar error message on Status most of my contrib modules are checked but Drupal is not verified.

Using drush hlp I got these output:

WD hacked: Could not download the project: Drupal core from URL: http://ftp.drupal.org/files/projects/drupal-7.15.tar.gz         [error]
WD hacked: Could not download project: Drupal core                                                                               [error]
WD hacked: Could not hash remote project: Drupal core                                                                            [error]
WD hacked: Could not download the project: Drupal core from URL: http://ftp.drupal.org/files/projects/drupal-7.15.tar.gz         [error]
WD hacked: Could not download project: Drupal core                                                                               [error]
WD hacked: Could not hash remote project: Drupal core                                                                            [error]
WD hacked: Could not hash local project: Drupal core                                                                             [error]
Ha ocurrido un error HTTP -1 al acceder a http://ftp.drupal.org/files/projects/drupal-7.15.tar.gz                                [error]
Ha ocurrido un error HTTP -1 al acceder a http://ftp.drupal.org/files/projects/drupal-7.15.tar.gz                                [error]
Done.
Invalid argument supplied for foreach() hacked.drush.inc:155                                                                     [warning]
 Title  Name  Version  Status  Changed  Deleted 

I've tried this in two diferent servers and i keep receiving the same output. Is posible to grab the files with wget, so they problem is not that isn't possible to have access to the files.

Any idea?

Seeing this on a site. After a bit of digging, the issue is that the release info returned by the update module upon which Hacked relies, doesn't contain all releases. I haven't had a chance to dig into this further, but one module that was failing was Libraries 1.0, and another was Menu Block 2.3. In the case of Libraries, that release is unsupported, but in the case of Menu Block, that is the current release.

I'd thought perhaps running cron would help, but it didn't. However, manually clearing the update module's cache (DELETE FROM cache_update) fixed the problem.

Hacked still fails to fetch dev releases that contain a version string similar to 7.x-3.0-beta1+4-dev.

@jhedstrom What version of Drupal core was this, 'they' keep changing the API and what's returned from update module, so it may have changed again, and I need to update.
Also, I'm not sure if we'll every support version strings like: 7.x-3.0-beta1+4-dev because they aren't entirely valid, and are a fruity Drush only construct, Drupal.org doesn't generate packages with such version numbers.

Oh wow, when did that happen!

I've created a new issue for handling this new info string format: #1835444: Support the new dev info strings

Actually, Drupal.org, and Drupal core in turn, support those version numbers. Drush just followed suite.

; Information added by drupal.org packaging script on 2012-09-30
version = "7.x-2.6+2-dev"
core = "7.x"
project = "date"
datestamp = "1348964349"

Also, the version of core for this particular site was 7.14.

Right...well if Drupal.org is able to provide these version numbers in the releases feed, then Hacked! should just work.

Not sure what is the current state, but I just noticed while auditing a website that the new format doesn't seem to work, I get "Unchecked" for all dev-modules which use the new format. Modules using the old format report as "Changed" which is not correct either, but there is another issue for the dev-versions of modules.

I can confirm this myself but it's happening with all contrib and drupal core as well, but I also get
WD hacked: Could not download project: Hacked! when running drush hd hacked

Setting to major since this actually makes the module not work as expected.

Same as #15.

Hi,
for me It was a path related issue. I'm testing the module on a local environment and in config, media, file system I've changed:
\xampp\tmp\tmp-drupal4test
to
/xampp/tmp/tmp-drupal4test
and now it works for all modules and core but not for hacked!

Trying with drush I get the same results: WD hacked: Could not hash local project: Hacked!

I've tried also changing "/xampp/tmp/tmp-drupal4test" with a more simple "tmp".

Reopening.

I am having the exact same issue as reported in #15 above, using 7.x-2.0-dev. 7.x-2.0-beta5 will pull some modules, but not all. 7.x-2.0-dev pulls none, not even drupal core.

I am able to download the specific version that the website I am auditing has installed (which is outdated, but available from d.o.) using drush dl module_name-7.x-specific-version-number. I'm not sure why Hacked! cannot download them.

all of a sudden I'm having similar problems :-/

did something about the drupal.org page change so to invoke this error?

same here.

I think i might've narrowed this down to the dev string being problematic.

however, I have one instance where it doesn't seem to be the dev string. I'm wondering if it is because it is an installation profile

After a debugging session, I'm confirming that this is because Hacked! can't find the dev version string in the list of available releases for the module. See #1835444: Support the new dev info strings.

I get this on projects that are not development versions

Adminimal Administration Menu 7.x-1.7
Backup and Migrate 7.x-3.1