Edit icon Edit This Page

Show the scan results of a package version

Show the vulnerability scan results of one version of a package.

Without flags it prints the overview: the status of the newest scan and the number of findings per severity of the newest COMPLETED scan (the counters stay the last known values while a rescan runs).

--history           the scan history of the version, newest first
--scan <id>         one scan (with --findings: the findings of that scan)
--findings          the findings of the newest scan (or of --scan)
--sort <p,dir>      sort the findings, for example severity,desc
cvssScore,desc or cveId,asc (Repsy Cloud sends no cvssScore)
--limit <n>         stop after n rows (0 means all)

–scope is the npm scope without the “@”.

In a Maven repository the artifact is groupId:artifactId (for example com.acme:app); the server finds nothing for the bare artifactId, so rp refuses it. The other formats take the plain package name.

–wait polls until the scan is COMPLETED or FAILED (the server has no status endpoint): first every –poll-interval, then slower, up to 15 seconds. It gives up after –timeout (default 10m) with a timeout error, which is NOT the threshold error: it exits 1, says nothing about the findings, and the scan keeps running on the server.

–fail-on critical|high|medium|low exits 5 when the scan has a finding at or above that severity; UNKNOWN findings never count. A scan that FAILED, or that is not final yet, cannot be judged: that is an error with exit 1, not a pass. Exit codes: 0 passed, 5 threshold reached, 1 timeout or other failure.

–wait and –fail-on apply to the overview only. Here –wait polls the overview of the version; it waits for the newest scan, whichever started it. If the version’s newest scan is an old COMPLETED one, –wait returns at once with its counters; in CI use ‘rp scan trigger –wait’ to judge the scan you started.

Examples:

rp scan show libs my-app 1.2.0
rp scan show libs my-app 1.2.0 --findings --sort severity,desc --limit 20
rp scan show libs my-app 1.2.0 --wait --fail-on critical
rp scan show <repo> <artifact> <version> [flags]

Options

      --fail-on string           Exit 5 when a finding has this severity or worse (critical, high, medium, low)
      --findings                 List the findings of the newest scan (or of --scan)
      --history                  List the scan history of the version
      --limit int                Stop after this many rows (0 means all)
      --poll-interval duration   First pause between polls; it grows up to 15s (with --wait) (default 2s)
      --scan string              Show this scan instead of the overview
      --scope string             npm scope, without the @
      --sort string              Sort the findings by property,asc|desc (cveId, severity, cvssScore, ...)
      --timeout duration         Give up waiting after this long (with --wait) (default 10m0s)
      --wait                     Wait until the scan is COMPLETED or FAILED

Options inherited from parent commands

      --api-url string           Panel API URL of the profile, overrides the stored value
      --ca-file string           PEM file with extra trusted CA certificates
      --debug                    Print debug output with secrets redacted
      --hostname string          Repsy host to use instead of the current profile
      --insecure                 Do not verify TLS certificates (unsafe; plain http is chosen with the URL, not with this flag)
      --insecure-storage         Keep credentials in a plain 0600 file instead of the OS keyring (unsafe; a warning is printed once per command)
      --jq string                Filter JSON output with a jq expression (implies --output json)
      --no-color                 Disable colored output
      --no-input                 Never prompt; fail when input is needed
      --output table|json|yaml   Output format: table, json or yaml (default table; json when --jq is given)
      --owner string             Owner segment of Cloud protocol URLs; --owner= means none
      --registry-url string      Protocol host URL of the profile, overrides the stored value
      --type os|cloud            Product of the host, overrides detection
      --web-url string           Panel UI URL of the profile (where /cli/auth lives), overrides the stored value
      --yes                      Answer yes to confirmation prompts

See also

  • rp scan - Trigger vulnerability scans and read their results
Found a problem with this page?