-
Notifications
You must be signed in to change notification settings - Fork 18
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 multiple repositories #165
Comments
We are referencing the Hackage namespace. In most cases, the package description contains a reference to the repository. In cases where it does not and a repository URL is known, I suggest using the existing |
Oh no I mean multiple repositories for security advisories, sorry! |
@MangoIV ok, thanks for clarifying. If I understand, we want the advisory data (or exported formats, e.g. OSV), to point back to content in this repo? |
yes; the idea would be that some independent entity could host their own set of security advisories and if a user so wishes, they can opt in to that repository as well and still, given an advisory, find its origin. |
Summary
it would be good to have the
Advisory
type point back to the repository it stems from; reason being thatThe text was updated successfully, but these errors were encountered: