-
-
Notifications
You must be signed in to change notification settings - Fork 25
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
Audit not executing if github url present in package.json #80
Comments
This is an npm issue not a better-npm-audit issue but since I hit this page through Google I might as well provide a solution. The latest versions of npm 6, 7, and 8 are all able to handle this situation. So update your npm. If you're just using whatever npm version came with Node.js then updating it wholesale would also solve your problem. It's specifically older versions of npm 6 that error out when git dependencies are present as far as I know. I'm not sure which version fixed this problem but this might be something that better-npm-audit would want to document. For context I ran into this same issue a while ago, though I use the |
Hi,
If in package.json github url is included then better-npm-audit throwing below error, any way is it possible to handle this scenario.
package.json
{ "name": "my application", "version": "1.0.0", "description": "Application", "main": "app.js", "scripts": { "start": "node app.js" }, "license": "UNLICENSED", "dependencies": { "body-parser": "^1.19.0", "compression": "^1.7.4", "config": "^3.3.7", "express": "^4.16.3", "request": "git+https://github.com/Sujay-shetty/request.git", "request-promise": "^4.2.2", "swagger-ui-express": "^4.4.0", "uuid": "^7.0.0" }, "devDependencies": { "@types/request-promise": "^4.1.46", "ts-node": "^8.9.1", "typescript": "^3.4.5" } }
Error :
![image](https://user-images.githubusercontent.com/7508108/170941574-18f60e5f-3f26-4b88-8a59-61e9f686ca86.png)
Could you please help me how to skip audit for github url or any custom url if it is present in package.json
Thanks,
Sujay
The text was updated successfully, but these errors were encountered: