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 multiple repositories #165

Open
MangoIV opened this issue Mar 17, 2024 · 4 comments
Open

support multiple repositories #165

MangoIV opened this issue Mar 17, 2024 · 4 comments

Comments

@MangoIV
Copy link
Contributor

MangoIV commented Mar 17, 2024

Summary

it would be good to have the Advisory type point back to the repository it stems from; reason being that

  1. we would like to refer to an advisory by an URL
  2. we would like to be able to have more than one source for the URL
@frasertweedale
Copy link
Collaborator

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 references field, with reference type PACKAGE, pointing to the repo.

@MangoIV
Copy link
Contributor Author

MangoIV commented Mar 17, 2024

Oh no I mean multiple repositories for security advisories, sorry!

@frasertweedale
Copy link
Collaborator

@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?

@MangoIV
Copy link
Contributor Author

MangoIV commented Mar 30, 2024

@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.

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