-
-
Notifications
You must be signed in to change notification settings - Fork 562
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
Incomplete/Incorrect result for yarn.lock and package-lock.json from package scan for pacakge that have '@' in namespace #1993
Comments
chinyeungli
changed the title
Imcomplete result for yarn.lock from package scan
Incomplete/Incorrect result for yarn.lock from package scan
Apr 2, 2020
chinyeungli
added a commit
that referenced
this issue
Apr 3, 2020
* The tool should now be able to parse the packages with namespace in yarn.lock correctly. Need to check for others such as package.lock etc.
chinyeungli
changed the title
Incomplete/Incorrect result for yarn.lock from package scan
Incomplete/Incorrect result for yarn.lock and package-lock.json from package scan for pacakge that have '@' in namespace
Apr 9, 2020
For the package-lock.json
The In addition,
which is incorrect as the |
chinyeungli
added a commit
that referenced
this issue
Apr 13, 2020
* Parse the namespace data for package-lock.json The weird (encoding related) character in purl has to be fixed in package_url.
4 tasks
chinyeungli
added a commit
that referenced
this issue
Apr 14, 2020
* The tool should now be able to parse the packages with namespace in yarn.lock correctly. Need to check for others such as package.lock etc. Signed-off-by: Chin Yeung Li <tli@nexb.com>
chinyeungli
added a commit
that referenced
this issue
Apr 14, 2020
* Parse the namespace data for package-lock.json The weird (encoding related) character in purl has to be fixed in package_url. Signed-off-by: Chin Yeung Li <tli@nexb.com>
chinyeungli
added a commit
that referenced
this issue
Apr 14, 2020
chinyeungli
added a commit
that referenced
this issue
Apr 14, 2020
Signed-off-by: Chin Yeung Li <tli@nexb.com>
pombredanne
added a commit
that referenced
this issue
Apr 15, 2020
Collect yarn.lock dependencies correctly #1993
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
With the following yarn.lock context
The tool parses the first 3 alright. However, it fails to parse the forth element
"@angular-builders/custom-webpack@^7.0.0":
, correctly. The following is the result:The expected result should be
In addition, the
lodash
does not exist in the output as well.Following is the complete output from the package scan for the above yarn.lock file:
The text was updated successfully, but these errors were encountered: