-
Notifications
You must be signed in to change notification settings - Fork 85
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
Integrate PurlDB in the UI navigation #1125
Comments
tdruez
added a commit
that referenced
this issue
Mar 22, 2024
Signed-off-by: tdruez <[email protected]>
tdruez
added a commit
that referenced
this issue
Mar 25, 2024
Signed-off-by: tdruez <[email protected]>
tdruez
added a commit
that referenced
this issue
Mar 25, 2024
Signed-off-by: tdruez <[email protected]>
tdruez
added a commit
that referenced
this issue
Mar 25, 2024
Signed-off-by: tdruez <[email protected]>
tdruez
added a commit
that referenced
this issue
Mar 25, 2024
Signed-off-by: tdruez <[email protected]>
tdruez
added a commit
that referenced
this issue
Mar 25, 2024
Signed-off-by: tdruez <[email protected]>
tdruez
added a commit
that referenced
this issue
Mar 25, 2024
Signed-off-by: tdruez <[email protected]>
tdruez
added a commit
that referenced
this issue
Mar 25, 2024
Signed-off-by: tdruez <[email protected]>
@pombredanne A new PurlDB tab is now displayed in the package details view when the PurlDB is properly defined in the app settings.
This process should happen on the PurlDB side. Any PURL requested in the PurlDB REST API that does not have a local match should be placed in a queue to be mined, scanned, and added to the PurlDB. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Here is a usecase that I would like to see supported: I imported an SBOM and while I navigate packages, there is a package that I would like to dive into.
I would like to:
This could be without updating the local data. Later one I would like also to update selectively, but this is may be best done in DejaCode.
The text was updated successfully, but these errors were encountered: