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 摘要。