Claus Ibsen created CAMEL-27340:
-----------------------------------

             Summary: camel-jbang - camel dependency audit checks the 
dependencies against OSV.dev and the Apache Camel security advisories
                 Key: CAMEL-27340
                 URL: https://issues.apache.org/jira/browse/CAMEL-27340
             Project: Camel
          Issue Type: New Feature
          Components: camel-jbang
            Reporter: Claus Ibsen
             Fix For: 4.24.0


The CVE Audit screen of camel-jbang (CAMEL-27328) checks the classpath of a 
running integration against OSV.dev and the Camel security advisories. The same 
check is not available as a command, for a script, a CI job or an AI agent: 
camel sbom only writes an SBOM for an external scanner, and the MCP dependency 
check only knows the Camel advisories.

A new command, {{camel dependency audit}}:

* audits the project in the current directory (as {{camel dependency list}}, 
with the transitive dependencies resolved), or a running integration 
({{--integration=<name or pid>}}, its real classpath)
* lists each CVE with its severity, CVSS score, the artifact, the version that 
fixes it, the dependency chain that brings it in, and whether the routes use it
* {{--by-artifact}}: one row per vulnerable JAR, with the version that fixes 
all its CVEs
* {{--json}}: one JSON document, for agents and scripts
* {{--severity}}: the lowest severity to list; {{--fail-on}}: exits 1 when a 
CVE at or above it is found (default: any), so a CI job fails
* {{--offline}}: only the Camel advisories of the catalog, no OSV.dev

The OSV.dev client and the scan move from the TUI plugin to camel-jbang-core, 
shared by the TUI, the CLI and the MCP server.

_Claude Code on behalf of Claus Ibsen_



--
This message was sent by Atlassian Jira
(v10.3.26#10030026)

Reply via email to