Add JSON schema for Package and Vulnerability metadata #11
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Member
keshav-space
commented
Jul 10, 2024
keshav-space
commented
- Resolves Create a schema to store vulnerability and package metadata serialized in a suitable JSON (or YAML) format #10
Signed-off-by: Keshav Priyadarshi <[email protected]>
keshav-space
force-pushed
the
10-vul-package-json-schema
branch
from
4d5046f to
0cfa261
Compare
pombredanne
reviewed
Jul 11, 2024
pombredanne
reviewed
Jul 11, 2024
Signed-off-by: Keshav Priyadarshi <[email protected]>
Signed-off-by: Keshav Priyadarshi <[email protected]>
Signed-off-by: Keshav Priyadarshi <[email protected]>
|
@keshav-space The push is missing the settings update with the various libraries you need? |
|
@keshav-space ignore this... config error on my part. Sorry for the churn! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.