kyberorg/Harbor Scan Report

Publish a Harbor image vulnerability scan report to PR comment

Trust Signals

Scorecard Score: not yet scored
Maintenance Recency: Stalelast commit Oct 4, 2022
License: Public domain

Pinned Snippet

workflow.ymlSHA-pinned

uses: kyberorg/harbor-scan-report@495f479fa56e5cdb178ce06cab61d78b7c710575 # v0.5.2

tags can be moved; commit SHAs can't. why a SHA?

Inputs

name	description	required	default
harbor-host	Hostname of your Harbor instance (without protocol).	yes	—
harbor-robot	Robot or Username to access Harbor with.	no	—
harbor-token	Robot's Token (or Username's password)	no	—
image	Image to scan (project/repo:tag[@digest])	yes	—
digest	Excepted SHA256 digest of image. Ignored, if digest is present in image. Format: 'sha256:01814f4b10f321f09244a919d34b0d5706d95624b4c69d75866bb9935a89582d'	no	—
max-allowed-severity	Minimum Vulnerability severity after which action considered as failed. Values: none, low, medium, high, critical	no	critical
report-sort-by	Sorting criteria for Vulnerability Report. Values: severity, score	no	severity
report-only-fixable	If set to true, Vulnerability Report will contain only items that have fix version	no	false
github-url	github.event.issue.comments_url - for issue, github.event.pull_request.comments_url - for PR	no	—
github-token	A GitHub personal access token used to commit to a branch on your behalf.	no	—
comment-title	Custom comment title	no	Docker Image Vulnerability Report
comment-mode	Create new comment or update exising. Possible values are: create_new, update_last	no	create_new
timeout	How long action should wait for image and scan report (in seconds)	no	120
check-interval	Time (in seconds) between retries. Valid for waiting for image appears in Harbor and waiting for report	no	5
harbor-proto	Protocol of Harbor instance. Use it, if your Harbor uses http	no	https
harbor-port	Custom port of Harbor instance. Use it, if Harbor instance has custom port	no	""

Outputs

no outputs