Skip to content
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

Provide info about configuration and project name for vulnerable dependency #265

Closed
ov7a opened this issue Jun 18, 2024 · 1 comment
Closed

Comments

@ov7a
Copy link
Member

ov7a commented Jun 18, 2024

Currently, the report looks like this:
image

While it's great that it points to settings.gradle.kts, but it's unclear from a get-go where exactly the dependency comes from (production/tests, direct/transitive, project/plugin/version catalog/included build/build logic etc)

It would be nice to have at least project name and configuration name in the description

@bigdaz
Copy link
Member

bigdaz commented Jun 21, 2024

We tried, but there's no mechanism in the GitHub Dependency Graph API to map a dependency to a particular project/configutration, without having a separate vulnerability alert reported for every project/configuration that uses the dependency.

This readme partly explains the reason for this: https://github.com/gradle/actions/blob/main/docs/dependency-submission-faq.md#why-arent-dependencies-be-linked-to-the-source-file-where-they-are-declared

The team at GitHub are aware of this limitation, and we've discussed plans to improve this in the future.

@bigdaz bigdaz closed this as completed Jun 21, 2024
@bigdaz bigdaz closed this as not planned Won't fix, can't repro, duplicate, stale Jun 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants