-
-
Notifications
You must be signed in to change notification settings - Fork 169
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
Feature/501 dependency tree for dotnet #532
Conversation
Hi. Could you rebase your branch and squash into a single commit?
|
b6955fa
to
2828667
Compare
2828667
to
d42d16e
Compare
Signed-off-by: Caroline Russell <caroline@appthreat.dev> Fix eslint error. Signed-off-by: Caroline Russell <caroline@appthreat.dev>
99eaca1
to
de3b6fe
Compare
Hi, I was just trying this out and wanted to know if this is expected behaviour. My
but the bom generated looks like this
I would have assumed that the top level package to look like this so that you can understand which are direct and which are the transitive deps.
Is this expected behaviour? Thank you! |
@noqcks We parse the projects.assets.json file to construct the tree. Could you check the dependencies section in that file? Also, would you be able to check with another independent tool, such as |
Looking at the projects.assets.json file for my project, I see we can extract
Looking at I suppose what im looking for is a way to have a distinction between direct dependencies, and all dependencies for a .NET application. This PR only support the latter from what I can see. Would be happy to create an issue and PR support for the former |
@noqcks, thank you. Sounds like a good proposal. @cerrussell, any thoughts on whether this is achievable? |
@prabhu I added a PR here for @cerrussell to review |
Closes #501
Adds parsing of dependency info from package.assets.json targets, including target dependency dependencies.