From 1dc84a8ad8a001a5723afae09d6d36bd29c6be54 Mon Sep 17 00:00:00 2001 From: swapnasagar pradhan Date: Fri, 6 Dec 2024 09:35:03 +0000 Subject: [PATCH] Update website/docs/design.md Co-authored-by: Ashna Mehrotra Signed-off-by: swapnasagar pradhan --- website/docs/design.md | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/website/docs/design.md b/website/docs/design.md index f92c7966..51709834 100644 --- a/website/docs/design.md +++ b/website/docs/design.md @@ -79,9 +79,8 @@ type PackageManager interface { The core architectural choice of using packages as the unit of patching creates several constraints: 1. **Package-Based Update Model**: - - While copa can work with or without vulnerability scanner reports, its patching capability is fundamentally based on package updates - - When using scanner reports, false positives/negatives from scanners flow downstream to copa - - The package-based approach limits the kinds of vulnerabilities copa can address to those fixable via package updates + - While Copa can work with or without vulnerability scanner reports, its patching capability is fundamentally based on os-level package updates + - When using scanner reports to perform a targeted patching of packages, false positives/negatives from scanners flow downstream to Copa 2. **Package Manager Dependencies**: - Copa depends on individual package manager adapters to correctly deploy patches to target images