remediation-planner

You can preview dependency remediation options for vulnerabilities without opening PRs by using a read-only planning approach. This method assesses and presents safe version upgrades based on findings, preventing unnecessary code modifications during the planning phase.

To plan vulnerability remediation using Endor findings, you utilize read-only data retrieval and analysis to assess dependency options. This approach leverages Endor's vulnerability evidence and version upgrades to recommend the best course of action.

Yes, you need Endor access to assess dependency remediation options. The planning process is intended for use within Endor's ecosystem and requires the endorctl dependency to retrieve and analyze vulnerability findings.

Yes, you can explore safe version upgrades for a flagged critical vulnerability before modifying code. This read-only planning process helps you understand potential remediation steps and dependency upgrades safely without direct code changes.

The best way to plan dependency remediation without creating merge requests is to use a read-only analysis approach. It safely explores available remediation options for identified vulnerabilities using Endor's findings without triggering any PRs or MRs.

The main limitation of read-only dependency remediation planning is that it prevents direct code modification. It is designed strictly for assessing and presenting options safely, meaning you cannot apply the actual version upgrades or fixes through this method.