Vulnerability Remediation
FeaturedTriages a dependency or container advisory against how your code actually uses it, proves whether the vulnerable path is reachable, and proposes the smallest change that closes it.
How it works
- Runs when: a new advisory affects a package your services carry.
- Finds every carrier: each service whose lockfile, image or transitive tree contains the package, including the base image.
- Decides reachability: one subagent per affected service, in parallel. A reachable verdict comes with the full path from entry point to vulnerable function as
file:linehops, and who supplies the input. - Rates your exposure: separately from the advisory's own severity. A critical CVE in code nothing calls is not a critical for you.
- You get: a ranked exposure report and the smallest pull request that removes the vulnerable version where it matters.
What it needs
- GitHub: read code and lockfiles, open pull requests
- Snyk (optional): read container findings