dequelabs / dequelabs/action-twistlock
Support configurable thresholds
Open
- Dominant language
- JavaScript
- Stars
- 1
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
Rather than requiring vulnerability thresholds be setup in the Twistlock console, we should support passing them to the action here.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reading the GitHub Action entry point and the code that invokes the Twistlock scan for a Docker image. Trace where vulnerability thresholds are currently assumed to come from the console; done means the action accepts configurable thresholds and passes them to the scan, with coverage for the new inputs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, github-actions, javascript
- Domain
- ci-cd, devops, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100