jfrog / jfrog/jfrog-cli-security

jf docker scan Fails Consistently on Previously Working Images Since 23/10/25

Open
#730 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
Go
Stars
13
Forks
50
Avg merge
3d 48m
Merged PRs (30d)
26

Description

Describe the bug

Hi,

On 25/10/21, we ran the following command successfully:
jf docker scan ${{ parameters.image }} --licenses --format=simple-json > ${{ parameters.outputFolder }}/${{ parameters.reportFilenamePrefix }}.jfrog.json
It worked without any issues, as it normally does.

However, on 23/10/25, we ran the same command with a different image, and it failed. Initially, we thought the problem was with the new image. But when we reran the exact same command as on 21/10/25 with the original image, it failed as well.

We have reproduced this issue locally multiple times, and it now occurs consistently.
Please find attached the debug logs from the failing runs for your reference.

Current behavior

➜ athena git:(dev) ✗ JFROG_CLI_LOG_LEVEL=DEBUG jf docker scan lightruncom/webapp:1.70.2-release.8c297ca52b --licenses --format=simple-json
16:50:58 [Debug] JFrog CLI version: 2.81.0
16:50:58 [Debug] OS/Arch: darwin/arm64
16:50:58 [Debug] Trace ID for JFrog Platform logs: 7efe466e22b4fa7b
16:50:58 [Debug] Using server-id configuration
16:50:58 [Debug] Sending HTTP GET request to: https://lightrun2024.jfrog.io/xray/api/v1/system/version
16:50:58 [Debug] Xray version: 3.131.4
16:50:58 [Debug] Sending HTTP GET request to: https://lightrun2024.jfrog.io/xray/api/v1/xsc/system/version
16:50:59 [Debug] XSC version: 3.999.999
16:50:59 [🔵Info] Log path: /Users/amitshkoory/.jfrog/logs/jfrog-cli.2025-10-26.16-50-59.77261.log
16:51:16 [🔵Info] Trace ID for JFrog Platform logs: 7efe466e22b4fa7b
16:51:16 [🚨Error] failed while parsing the response from Xray: violation doesn't have any components

jfrog-cli.2025-10-26.16-50-59.77261.log
debug-logs.log

Reproduction steps

latest jfrog cli version
+
jf docker scan ${{ parameters.image }} --licenses --format=simple-json > ${{ parameters.outputFolder }}/${{ parameters.reportFilenamePrefix }}.jfrog.json

Expected behavior

A log from working ran is attached.

JFrog CLI version

2.81.0

Operating system type and version

Linux

JFrog Artifactory version

SaaS

JFrog Xray version

SaaS

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing jf docker scan with --licenses --format=simple-json and review the attached debug logs, focusing on the Xray response that reports “violation doesn't have any components.” Trace the CLI's response-parsing entry point and verify completion against the expected JSON output and the previously working run.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, go
Domain
api, cli, security
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.