upwindsecurity/Upwind Security Image Scanning

Scan against built images

View on GitHub

Trust Signals

Scorecard Score
not yet scored
Maintenance Recency
Stale
License
None
namedescriptionrequireddefault
upwind_client_idUpwind Client IDyes
upwind_client_secretUpwind Client Secretyes
docker_imageAlready built docker image residing on same runneryes
docker_userUser to authenticate to the Docker registryno
docker_passwordPassword to authenticate to the Docker registryno
pull_imageAttempt to pull the image. Set to false if image is available locallytrue
oci_clientClient with which to pull image. Options are docker (default), podman, and skopeodocker
additional_registriesComma-separated list of additional registries to associate with the scanned image, passed as a stringno
output_jsonFile location to write JSON output tooutput.json
commit_shaSHA to be associated with the build. By default this uses the $GITHUB_SHA environmental variableno${GITHUB_SHA}
upwind_uriPublic Upwind URI domain namenoupwind.io
use_sudowhether to use sudo when invoking the scan to connect to the OCI clientnotrue
github_tokenGitHub token for authenticationno
pr_numberPull request numberno
repo_nameThe GitHub repository in owner/repo formatno
add_commentWhether to add a comment to the PR when a scan is completednofalse
perform_multiarchitecture_image_scanWhether to perform a multi-arch image scan or not, defaulted to truenotrue
debugEnable debug loggingfalse
main_branchBase/target branch to diff against (e.g. the PR's base branch, typically github.event.pull_request.base.ref). When set, introduced/resolved CVEs are computed vs the latest scanned image of this branch instead of the previously scanned image. Requires that branch to have been scanned.no
pr_idPull request identifier associated with the scan (optional)no
pr_linkPull request URL associated with the scan (optional)no
block_onBlock workflow based on Upwind Scan Recommendation. Can be either 'do_not_deploy' or 'deploy_with_caution'

no outputs