Image vulnerability scanning

未關閉
#266 0 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

維護者通常 1 天內回覆

還沒有人認領這個 Issue。

評估

難度
5/5
預估耗時
一週以上
新手友好度
35/100
Issue 類型
功能
描述清晰度
基本清楚
活躍度
活躍
技術堆疊
devops, docker, typescript
領域
devops, security

研究方向

Read the Screen 23 design and inspect the agent and control plane entry points to understand where images are built and deployed; the issue does not name specific files or tests. First resolve which scanner to use, its license, and where scanning runs, then define how the threshold fits deployment. Done means known CVEs appear with severity and fixed version, and deployments are blocked above the configured threshold.

由索引模型根據 Issue 內容生成。

描述

needs-decision priority:P2 task track:agent track:control-plane track:web
Track

A: agent, C: control plane, W: web UI

Scope
  • Screen 23 of the design (preview): scan each built image (the design names Trivy), list CVEs by severity, optionally block deploys above a threshold.
  • Needs a decision on the scanner and its license, and on where the scan runs.
Acceptance criteria

A built image with a known CVE shows it with severity and fixed version; the blocking threshold is enforced when enabled.

Depends on

M3.3

主要語言
TypeScript
星號
2
分支
1
平均合併
7 小時 17 分鐘
30 天內合併 PR
197

環境準備

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

shipkeepdev/shipkeep 的其他 Issue

查看 shipkeepdev/shipkeep 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。