jf scan throws "sca graph scan" error when scanning generic JAR
Los mantenedores suelen responder en 2 días
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 3/5
- Tiempo estimado
- 1-2 días
- Aptitud para principiantes
- 55/100
Línea de trabajo
Reproduce the failure with jf scan "json.jar" and with --sca --without-contextual-analysis, then trace the CLI security scan path that submits the SCA graph request. Done means a generic JAR with no dependency metadata completes without the nodes validation error, while normal scans continue to work.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Describe the bug
When running jf scan and providing JAR files containing class files + MANIFEST.MF but no other dependency, maven, or other project information, xray throws an error even when not requesting to run an SCA scan.
14:06:35 [🚨Error] target 'json.jar [unknown]' errors:
sca scanning 'generic://sha256:d7c7b242bbe4e16743cefeff8effa1bc685a0eb6a4d8a0d575de55d79270dfc0/json.jar' failed with error: server response: 400 Bad Request
"sca graph scan request is not valid: the field 'nodes' is required"
Current behavior
2026-10-02T14:27:21.437Z [jfxia] [DEBUG] [] [archive_mgr:732 ] [UnnamedContext ] No classification found for json.jar, classified as generic [flow_origin][cli_indexer_app]
2026-10-02T14:27:21.437Z [jfxia] [DEBUG] [] [archive_mgr:738 ] [UnnamedContext ] json.jar was classified as Generic [flow_origin][cli_indexer_app]
2026-10-02T14:27:21.437Z [jfxia] [DEBUG] [] [utils:442 ] [UnnamedContext ] total running time for indexing tree construction of json.jar: 9.3747e-05 seconds [flow_origin][cli_indexer_app]
2026-10-02T14:27:21.437Z [jfxia] [INFO ] [] [archive_mgr:356 ] [UnnamedContext ] finished walking artifact files: artifact:/json.jar, sha256:d7c7b242bbe4e16743cefeff8effa1bc685a0eb6a4d8a0d575de55d79270dfc0, filteredOut:0, inspected:26, archivesOpened:0, archivesNotOpened:0 [flow_origin][cli_indexer_app]
2026-10-02T14:27:21.437Z [jfxia] [DEBUG] [] [utils:442 ] [UnnamedContext ] total running time for indexing json.jar: 0.00163604 seconds [flow_origin][cli_indexer_app]
2026-10-02T14:27:21.689Z [jfxia] [DEBUG] [] [refiner:259 ] [UnnamedContext ] returned from external 0 comps [flow_origin][cli_indexer_app]
14:27:21 [Debug] Sending HTTP POST request to: https://XXX.jfrog.io/xray/api/v1/xsc/sca/scan/graph?multi_scan_id=XXX&scan_type=binary
14:27:21 [Debug] Sending HTTP PUT request to: https://XXX.jfrog.io/xray/api/v1/xsc/event
14:27:22 [Debug] Command event:
{{0 failed 0 0 false 6.919976092s } XXX [] }
14:27:22 [🔵Info] Trace ID for JFrog Platform logs: XXX
14:27:22 [🚨Error] target 'json.jar [unknown]' errors:
sca scanning 'generic://sha256:d7c7b242bbe4e16743cefeff8effa1bc685a0eb6a4d8a0d575de55d79270dfc0/json.jar' failed with error: server response: 400 Bad Request
"sca graph scan request is not valid: the field 'nodes' is required"
Reproduction steps
The same results with:
jf scan "json.jar"
and
jf scan "json.jar" --sca --without-contextual-analysis
Expected behavior
As the JAR is generic and does not appear to match any vulnerabilities, the scan should continue without error
JFrog CLI-Security version
3.999.999
JFrog CLI version (if applicable)
2.125.0
Operating system type and version
RHEL 8.10
JFrog Xray version
3.154.11
- Lenguaje dominante
- Go
- Estrellas
- 13
- Forks
- 52
- Merge medio
- 2 d 9 h
- PR fusionados (30 d)
- 21
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de jfrog/jfrog-cli-security
-
bug
Dificultad 3/5 1-2 días Aptitud para principiantes 68/100
jfrog/jfrog-cli-security#904 ·
Los mantenedores suelen responder en 2 días
-
feature request
Dificultad 3/5 1-2 días Aptitud para principiantes 68/100
jfrog/jfrog-cli-security#893 ·
Los mantenedores suelen responder en 2 días
-
bug
Dificultad 4/5 3-5 días Aptitud para principiantes 45/100
jfrog/jfrog-cli-security#871 · 1 comentario ·
Los mantenedores suelen responder en 2 días
-
bug
Dificultad 3/5 1-2 días Aptitud para principiantes 48/100
jfrog/jfrog-cli-security#817 ·
Los mantenedores suelen responder en 2 días
-
feature request
Dificultad 3/5 1-2 días Aptitud para principiantes 68/100
jfrog/jfrog-cli-security#824 ·
Los mantenedores suelen responder en 2 días
Todos los issues de jfrog/jfrog-cli-security
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
Los mantenedores suelen responder en 1 día
-
enhancement
Dificultad 1/5 1-3 horas Aptitud para principiantes 76/100
superplanehq/superplane#9007 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
yetone/magpie#3905 · 1 comentario ·
Los mantenedores suelen responder en 1 día