io.jenkins:configuration-as-code (maven) has 9 known vulnerabilities, the worst rated HIGH. Upgrade to 1.47.1 or later to clear all of them. No malicious-package signal is recorded.
// questionsIs io.jenkins:configuration-as-code safe to install?
CyberXYZ does not call a package safe in absolute terms. It records 9 known vulnerabilities for io.jenkins:configuration-as-code (maven), the worst rated HIGH, and no malicious-package signal. Whether it is acceptable depends on the version you run.
Does io.jenkins:configuration-as-code have known vulnerabilities?
Yes. CyberXYZ records 9 known vulnerabilities for io.jenkins:configuration-as-code (maven), the worst rated HIGH. These include GHSA-8486-h39x-cx2f, GHSA-5r6p-p9r6-r326, GHSA-vwq9-cmqr-3c8c, GHSA-ggmx-pq89-7mcr, GHSA-7c3v-vc3x-x789.
Which version of io.jenkins:configuration-as-code should I use?
1.47.1 or later clears every advisory recorded for io.jenkins:configuration-as-code (maven). Check the release you pick before installing it.
How do I check io.jenkins:configuration-as-code before installing?