-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
403 returned from NVD #6157
Comments
Seeing the same issue with pnpm owasp-dependency-check which is now downloading
NOTE: since the node package downloads the latest version from Github independently of the version of the package, all node projects will now be dead in the water as they have no way of pinning the version back. Essentially, the blast radius of this regression is pretty large. |
Also facing this issue
|
See #6149 |
@jeremylong I reviewed the other issue, on the surface it looks different than this one. We're seeing a 403, not a 5xx error, is this the same problem? #6149 is currently open, I am trying to determine if I need to take any additional action right now or wait and monitor that issue. What is your recommendation? |
@michalszelagsonos It seems to me that the API is blocked generally at the moment, and they are not issuing new keys. Hence these issues have been collated into one |
I'm trying to upgrade my maven dependency check plugin to 9.0.1. Here's my maven setup:
I've even added "-DnvdApiKey=..." to my run command. |
Encountering the same. Are we sure this 403 is a duplicate of all the other http error responses? |
Describe the bug
calling dependencyCheckAnalyze from gradle plugin returns 403
Version of dependency-check used
Using 9.0.1 of gradle plugin with jdk 21.
Log file
The text was updated successfully, but these errors were encountered: