oscerd opened a new issue, #3073: URL: https://github.com/apache/camel-kamelets/issues/3073
`pqc-signature-action` and `pqc-kem-action` route to `pqc:sign` and `pqc:kem`, but their `spec.dependencies` declare `camel:http`, `camel:kamelet` and `camel:core`, not `camel:pqc`. Neither template uses an HTTP endpoint: `camel:http` has been there since the first PQC Kamelet and was carried over to the KEM one. Because the catalog SBOM is generated from `spec.dependencies`, `camel-kamelets-sbom/camel-kamelets-catalog-sbom.json` currently records both Kamelets as depending on `camel-http` and never lists `camel-pqc`: ``` kamelet:pqc-kem-action -> camel-core, camel-http, camel-kamelet kamelet:pqc-signature-action -> camel-core, camel-http, camel-kamelet ``` so the weekly Catalog Dependency Scan attributes camel-http findings to them and never checks camel-pqc, whose Bouncy Castle dependency is the one that matters for these Kamelets. Expected: `camel:pqc` in place of `camel:http` in both Kamelets. _Claude Code on behalf of oscerd_ -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
