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

docs(guided remediation): document override strategy for Maven remediation #1181

Draft
wants to merge 8 commits into
base: main
Choose a base branch
from

Conversation

michaelkedar
Copy link
Member

@michaelkedar michaelkedar added the guided remediation Related to guided remediation / osv-scanner fix label Aug 14, 2024
@codecov-commenter
Copy link

codecov-commenter commented Aug 14, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 67.82%. Comparing base (981b0b5) to head (aa3cb75).

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1181      +/-   ##
==========================================
+ Coverage   67.81%   67.82%   +0.01%     
==========================================
  Files         174      174              
  Lines       16769    16769              
==========================================
+ Hits        11372    11374       +2     
+ Misses       4767     4766       -1     
+ Partials      630      629       -1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

{: .note }
The `override` strategy is currently only supported in `--non-interactive` mode.

Maven allows for the version specification of direct and indirect dependencies to be overwritten by a POM's `<dependencyManagement>`. This mechanism can be used to force a vulnerable dependency to be updated to a newer, non-vulnerable version. Overriding dependency versions can enable otherwise inaccessible updates, but it also risks breaking the application if the new version is incompatible with other dependencies.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We update the normal <dependencies> section if it already exists there right?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, I'll adjust the wording


| File Format | Supported [Remediation Strategies](#remediation-strategies) |
| :---------------------------------------------- | :---------------------------------------------------------- |
| `package-lock.json` lockfile | [`in-place`](#in-place-lockfile-remediation) |
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

probably also worth spelling out the package ecosystem in (new) first column?

```

<details markdown="1">
<summary><b>Sample override output</b></summary>
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

TODO: regenerate output with #1210

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
guided remediation Related to guided remediation / osv-scanner fix
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants