-
Notifications
You must be signed in to change notification settings - Fork 456
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
Add support for scanning dependencies in package.json #1453
Comments
As we already have a json parser, should we add support for package.json as an add-on for the json parser (as package.json at it's core is just "json"), or should we create a new parser which would specially deal with files named "package.json"? |
@XDRAGON2002 I have a working prototype function which scans the package.json file and extracts the packages and version numbers before finding the vendor. However there needs to be better product/vendor matching which #1504 is in the process of resolving. I think it needs to be separate to the json parser although I will look at this to see if can be used. |
That's great! |
Add support for javascript dependencies included in package.json.
File format is described in [https://docs.npmjs.com/cli/v8/configuring-npm/package-json#dependencies]
The text was updated successfully, but these errors were encountered: