LizardByte / LizardByte/roadmap
.github: scan docker images with Dive/Dockle
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 2
- Forks
- 0
- Avg merge
- 25m
- Merged PRs (30d)
- 5
Description
### Is there an existing issue for this item?
- [x] I have searched the existing issues
### Repositories
LizardByte/.github
### Languages/Skills/Technologies
Docker, GitHub actions
### Description
The idea is to modify our global `ci-docker.yml` workflow to scan images with Dive and/or Dockle
### Estimated Effort
effort:Medium
### Priority
priority:Low
### Target Milestone
6+ months
### Dependencies
_No response_
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the global ci-docker.yml workflow and review how Docker images are currently built. Determine where Dive and/or Dockle scans should run, then verify that the workflow performs the requested image scanning successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, github-actions
- Domain
- ci-cd, devops, security
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100