Possibly incorrect security status in VersionEye

[crc442]

VersionEye still shows all versions of growl as vulnerable (https://www.versioneye.com/nodejs/growl/1.10.2), but I believe that is not true and the bug was fixed in > v1.9.3 (#62), right?
Is there anything we/I can do correct VersionEye? This is kinda breaking our builds.

[deiga]

@crc442 Thanks for the heads up. It seems that the NSP advisory was still in effect. I submitted a request to take it down :)

[reiz]

@crc442 @deiga For NodeJS projects VersionEye is getting the security data from NodeSecurity.io and Snyk.io. If it's fixed in their database it should be fixed in our database as well. But I will double check it today.

[reiz]

@crc442 @deiga In the NodeSecurity.io database it's marked as solved for verison >=1.10.2. I updated our database with that. The newest version is green now: https://www.versioneye.com/nodejs/growl/1.10.2.