Installing "SharpHound.fireeye v1.0.0.7" failed with 404

[UnwantedFeature]

Describe the bug and expected behavior Installing "SharpHound.fireeye v1.0.0.7" failed with 404. Possible reason: The repository "SharpHound" does not exist anymore. It was separated into SharpHound2 (deprecated) and SharpHound3

Version

• OS: Win10 Pro x64

PS C:\Windows\system32 > cinst -y SharpHound.fireeye
Chocolatey v0.10.15
Installing the following packages:
SharpHound.fireeye
By installing you accept licenses for the packages.
Progress: Downloading SharpHound.fireeye 1.0.0.7... 100%

SharpHound.fireeye v1.0.0.7
sharphound.fireeye package files install completed. Performing other installation steps.
Attempt to get headers for https://github.com/BloodHoundAD/SharpHound/archive/41516e778ea186e144e4494f2e070cdb9aa878b9.zip failed.
  The remote file either doesn't exist, is unauthorized, or is forbidden for url 'https://github.com/BloodHoundAD/SharpHound/archive/41516e778ea186e144e4494f2e070cdb9aa878b9.zip'. Exception calling "GetResponse" with "0" argument(s): "The remote server returned an error: (404) Not Found."
Downloading SharpHound.fireeye
  from 'https://github.com/BloodHoundAD/SharpHound/archive/41516e778ea186e144e4494f2e070cdb9aa878b9.zip'
ERROR: The remote file either doesn't exist, is unauthorized, or is forbidden for url 'https://github.com/BloodHoundAD/SharpHound/archive/41516e778ea186e144e4494f2e070cdb9aa878b9.zip'. Exception calling "GetResponse" with "0" argument(s): "The remote server returned an error: (404) Not Found."
The install of sharphound.fireeye was NOT successful.
Error while running 'C:\ProgramData\chocolatey\lib\SharpHound.fireeye\Tools\chocolateyInstall.ps1'.
 See log for details.

Chocolatey installed 0/1 packages. 1 packages failed.
 See the log for details (C:\ProgramData\chocolatey\logs\chocolatey.log).

Failures
 - sharphound.fireeye (exited 404) - Error while running 'C:\ProgramData\chocolatey\lib\SharpHound.fireeye\Tools\chocolateyInstall.ps1'.
 See log for details.
COMMANDO 16.07.2021 11:00:49

[day1player]

Thank you for the issue, I will be able to get this fixed today 😄

[nos3curity]

Fixed the issue in the upcoming release of Commando planned for later this summer.