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

Support github releases / packages / advisories #474

Open
edulix opened this issue Jul 5, 2022 · 2 comments
Open

Support github releases / packages / advisories #474

edulix opened this issue Jul 5, 2022 · 2 comments

Comments

@edulix
Copy link

edulix commented Jul 5, 2022

This might sound like an obvious question and maybe I'm wrong and this is supported or I didn't read the documentation correctly.

But I think it would be great if the Advisory Database integrated with Github Releases, Github Packages and Github Advisories for Github Projects.

# Use case

This could work well with dependabot and the new Dependency submission API. For example, I'm using Nix. Nix as a package manage does not typically use a centralized registry and rather uses "channels" that contain packages.

However, nix packages many times fetch the sources from github. With the dependency submission API, a given nix dependency could be reported to be from github (or other supported ecosystem such as npm) and dependabot now would be able to report security vulnerability for nix dependencies.

@KateCatlin
Copy link
Collaborator

Hey @edulix thank you for reaching out! This is a really cool idea and speaks to a future we'd like to someday get to. I'm going to keep the issue open for others to comment and upvote.

@rjaegers
Copy link

I second this; recently I helped implement a dependency scanner that takes CMake files as input and submits dependencies to the Dependency Submission API (https://github.com/philips-forks/cmake-dependency-submission). I would have liked a more-native "feel" for package type "github". Now, when generating an SBOM for example, the package type is translated to "unknown". So no Dependabot support, no security advisories. That was a bit disappointing.

I think great value can be had by supporting the "github" purl type.

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

3 participants