Add vulnerability management commands #12
Merged
+9,316
−152
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
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
andrew
force-pushed
the
vulns-subcommand
branch
4 times, most recently
from
d28741d to
d48c9d6
Compare
…ties and their statuses
andrew
force-pushed
the
vulns-subcommand
branch
from
d48c9d6 to
37e790a
Compare
…ove exposure analysis
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.
Adds
git pkgs vulnscommand for tracking vulnerabilities in your dependencies over time.Subcommands:
sync- fetch vulnerability data from OSV for packages in your lockfilesblame- find who introduced a vulnerable dependencypraise- find who fixed a vulnerabilityexposure- show how long vulnerabilities were present before being fixeddiff- compare vulnerabilities between commitslog- show vulnerability changes across commit historyhistory- track a specific vulnerability's lifecycleshow- display details about a vulnerabilityThe vulnerability data is stored in the git-pkgs SQLite database alongside package history, enabling git-style queries against your security posture over time.
Contains parts of #3 as well