Image vulnerability scanning

Open
  • Is something wrong?
#266 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
devops, docker, typescript
Domain
devops, security

Research direction

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.

Written by the indexing model from the issue text.

Description

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

Dominant language
TypeScript
Stars
2
Forks
1
Avg merge
7h 17m
Merged PRs (30d)
197

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from shipkeepdev/shipkeep

All issues in shipkeepdev/shipkeep

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.