Skip to content
Lint PR

feat: Add possibility to configure probes for each pod #44

Sign in to view logs

feat: Add possibility to configure probes for each pod

feat: Add possibility to configure probes for each pod #44

Triggered via pull request January 31, 2024 13:27
@ppawlowskippawlowski
opened #291
Status Success
Total duration 13s
Artifacts –

lint-pr.yaml

on: pull_request_target
Validate PR title
4s
Validate PR title
Fit to window
Zoom out
Zoom in

Annotations

71 warnings
Validate PR title
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: amannn/action-semantic-pull-request@v5. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
[MEDIUM] CVE-2023-6237 (libcrypto3-3.1.4-r3) failed: libcrypto3-3.1.4-r3#L0
trivy-junit-results.xml
[MEDIUM] CVE-2023-6237 (libssl3-3.1.4-r3) failed: libssl3-3.1.4-r3#L0
trivy-junit-results.xml
[MEDIUM] CVE-2023-6237 (openssl-3.1.4-r3) failed: openssl-3.1.4-r3#L0
trivy-junit-results.xml
[HIGH] CVE-2022-4450 (libcrypto1.1-1.1.1n-r0) failed: libcrypto1.1-1.1.1n-r0#L0
trivy-junit-results.xml
[HIGH] CVE-2023-0215 (libcrypto1.1-1.1.1n-r0) failed: libcrypto1.1-1.1.1n-r0#L0
trivy-junit-results.xml
[HIGH] CVE-2023-0286 (libcrypto1.1-1.1.1n-r0) failed: libcrypto1.1-1.1.1n-r0#L0
trivy-junit-results.xml
[HIGH] CVE-2023-0464 (libcrypto1.1-1.1.1n-r0) failed: libcrypto1.1-1.1.1n-r0#L0
trivy-junit-results.xml
[MEDIUM] CVE-2022-2097 (libcrypto1.1-1.1.1n-r0) failed: libcrypto1.1-1.1.1n-r0#L0
trivy-junit-results.xml
[MEDIUM] CVE-2022-4304 (libcrypto1.1-1.1.1n-r0) failed: libcrypto1.1-1.1.1n-r0#L0
trivy-junit-results.xml
[MEDIUM] CVE-2023-0465 (libcrypto1.1-1.1.1n-r0) failed: libcrypto1.1-1.1.1n-r0#L0
trivy-junit-results.xml
[HIGH] CVE-2022-4450 (libssl1.1-1.1.1n-r0) failed: libssl1.1-1.1.1n-r0#L0
trivy-junit-results.xml
[HIGH] CVE-2023-0215 (libssl1.1-1.1.1n-r0) failed: libssl1.1-1.1.1n-r0#L0
trivy-junit-results.xml
[HIGH] CVE-2023-0286 (libssl1.1-1.1.1n-r0) failed: libssl1.1-1.1.1n-r0#L0
trivy-junit-results.xml
[HIGH] CVE-2023-0464 (libssl1.1-1.1.1n-r0) failed: libssl1.1-1.1.1n-r0#L0
trivy-junit-results.xml
[MEDIUM] CVE-2022-2097 (libssl1.1-1.1.1n-r0) failed: libssl1.1-1.1.1n-r0#L0
trivy-junit-results.xml
[MEDIUM] CVE-2022-4304 (libssl1.1-1.1.1n-r0) failed: libssl1.1-1.1.1n-r0#L0
trivy-junit-results.xml
[MEDIUM] CVE-2023-0465 (libssl1.1-1.1.1n-r0) failed: libssl1.1-1.1.1n-r0#L0
trivy-junit-results.xml
[CRITICAL] CVE-2022-37434 (zlib-1.2.12-r0) failed: zlib-1.2.12-r0#L0
trivy-junit-results.xml
[MEDIUM] CVE-2023-45857 (axios-0.27.0) failed: axios-0.27.0#L0
trivy-junit-results.xml
[MEDIUM] CVE-2023-26159 (follow-redirects-1.15.3) failed: follow-redirects-1.15.3#L0
trivy-junit-results.xml
[MEDIUM] CVE-2022-33987 (got-11.8.3) failed: got-11.8.3#L0
trivy-junit-results.xml
[HIGH] CVE-2022-25881 (http-cache-semantics-4.1.0) failed: http-cache-semantics-4.1.0#L0
trivy-junit-results.xml
[MEDIUM] GHSA-v78c-4p63-2j6c (moment-timezone-0.5.34) failed: moment-timezone-0.5.34#L0
trivy-junit-results.xml
[MEDIUM] CVE-2022-25896 (passport-0.5.2) failed: passport-0.5.2#L0
trivy-junit-results.xml
[HIGH] CVE-2022-24999 (qs-6.9.6) failed: qs-6.9.6#L0
trivy-junit-results.xml
[MEDIUM] CVE-2022-25883 (semver-7.3.5) failed: semver-7.3.5#L0
trivy-junit-results.xml
[MEDIUM] CVE-2022-25883 (semver-7.3.7) failed: semver-7.3.7#L0
trivy-junit-results.xml
[MEDIUM] CVE-2023-26136 (tough-cookie-4.0.0) failed: tough-cookie-4.0.0#L0
trivy-junit-results.xml
[MEDIUM] CVE-2023-0842 (xml2js-0.4.23) failed: xml2js-0.4.23#L0
trivy-junit-results.xml
[MEDIUM] GHSA-v78c-4p63-2j6c (moment-timezone-0.5.34) failed: moment-timezone-0.5.34#L0
trivy-junit-results.xml
All 2 runs failed: [MEDIUM] CVE-2022-25883 (semver-7.3.7): semver-7.3.7#L0
trivy-junit-results.xml
[MEDIUM] CVE-2023-26136 (tough-cookie-4.0.0) failed: tough-cookie-4.0.0#L0
trivy-junit-results.xml
[MEDIUM] CVE-2023-0842 (xml2js-0.4.23) failed: xml2js-0.4.23#L0
trivy-junit-results.xml
[HIGH] DS002 (Dockerfile Security Check) failed: Dockerfile Security Check#L0
trivy-junit-results.xml
[MEDIUM] GHSA-v78c-4p63-2j6c (moment-timezone-0.5.34) failed: moment-timezone-0.5.34#L0
trivy-junit-results.xml
All 2 runs failed: [MEDIUM] CVE-2022-25883 (semver-7.3.7): semver-7.3.7#L0
trivy-junit-results.xml
[MEDIUM] CVE-2023-26136 (tough-cookie-4.0.0) failed: tough-cookie-4.0.0#L0
trivy-junit-results.xml
[MEDIUM] CVE-2023-0842 (xml2js-0.4.23) failed: xml2js-0.4.23#L0
trivy-junit-results.xml
[HIGH] CVE-2022-4450 (libcrypto1.1-1.1.1n-r0) failed: libcrypto1.1-1.1.1n-r0#L0
trivy-junit-results.xml
[HIGH] CVE-2023-0215 (libcrypto1.1-1.1.1n-r0) failed: libcrypto1.1-1.1.1n-r0#L0
trivy-junit-results.xml
[HIGH] CVE-2023-0286 (libcrypto1.1-1.1.1n-r0) failed: libcrypto1.1-1.1.1n-r0#L0
trivy-junit-results.xml
[HIGH] CVE-2023-0464 (libcrypto1.1-1.1.1n-r0) failed: libcrypto1.1-1.1.1n-r0#L0
trivy-junit-results.xml
[MEDIUM] CVE-2022-2097 (libcrypto1.1-1.1.1n-r0) failed: libcrypto1.1-1.1.1n-r0#L0
trivy-junit-results.xml
[MEDIUM] CVE-2022-4304 (libcrypto1.1-1.1.1n-r0) failed: libcrypto1.1-1.1.1n-r0#L0
trivy-junit-results.xml
[MEDIUM] CVE-2023-0465 (libcrypto1.1-1.1.1n-r0) failed: libcrypto1.1-1.1.1n-r0#L0
trivy-junit-results.xml
[HIGH] CVE-2022-4450 (libssl1.1-1.1.1n-r0) failed: libssl1.1-1.1.1n-r0#L0
trivy-junit-results.xml
[HIGH] CVE-2023-0215 (libssl1.1-1.1.1n-r0) failed: libssl1.1-1.1.1n-r0#L0
trivy-junit-results.xml
[HIGH] CVE-2023-0286 (libssl1.1-1.1.1n-r0) failed: libssl1.1-1.1.1n-r0#L0
trivy-junit-results.xml
[HIGH] CVE-2023-0464 (libssl1.1-1.1.1n-r0) failed: libssl1.1-1.1.1n-r0#L0
trivy-junit-results.xml
[MEDIUM] CVE-2022-2097 (libssl1.1-1.1.1n-r0) failed: libssl1.1-1.1.1n-r0#L0
trivy-junit-results.xml
[MEDIUM] CVE-2022-4304 (libssl1.1-1.1.1n-r0) failed: libssl1.1-1.1.1n-r0#L0
trivy-junit-results.xml
[MEDIUM] CVE-2023-0465 (libssl1.1-1.1.1n-r0) failed: libssl1.1-1.1.1n-r0#L0
trivy-junit-results.xml
[CRITICAL] CVE-2022-37434 (zlib-1.2.12-r0) failed: zlib-1.2.12-r0#L0
trivy-junit-results.xml
[MEDIUM] CVE-2023-45857 (axios-0.27.0) failed: axios-0.27.0#L0
trivy-junit-results.xml
[MEDIUM] CVE-2023-26159 (follow-redirects-1.15.3) failed: follow-redirects-1.15.3#L0
trivy-junit-results.xml
[MEDIUM] CVE-2022-33987 (got-11.8.3) failed: got-11.8.3#L0
trivy-junit-results.xml
[HIGH] CVE-2022-25881 (http-cache-semantics-4.1.0) failed: http-cache-semantics-4.1.0#L0
trivy-junit-results.xml
[MEDIUM] GHSA-v78c-4p63-2j6c (moment-timezone-0.5.34) failed: moment-timezone-0.5.34#L0
trivy-junit-results.xml
[MEDIUM] CVE-2022-25896 (passport-0.5.2) failed: passport-0.5.2#L0
trivy-junit-results.xml
[HIGH] CVE-2022-24999 (qs-6.9.6) failed: qs-6.9.6#L0
trivy-junit-results.xml
[MEDIUM] CVE-2022-25883 (semver-7.3.5) failed: semver-7.3.5#L0
trivy-junit-results.xml
[MEDIUM] CVE-2022-25883 (semver-7.3.7) failed: semver-7.3.7#L0
trivy-junit-results.xml
[MEDIUM] CVE-2023-26136 (tough-cookie-4.0.0) failed: tough-cookie-4.0.0#L0
trivy-junit-results.xml
[MEDIUM] CVE-2023-0842 (xml2js-0.4.23) failed: xml2js-0.4.23#L0
trivy-junit-results.xml
[MEDIUM] CVE-2023-6237 (libcrypto3-3.1.4-r3) failed: libcrypto3-3.1.4-r3#L0
trivy-junit-results.xml
[MEDIUM] CVE-2023-6237 (libssl3-3.1.4-r3) failed: libssl3-3.1.4-r3#L0
trivy-junit-results.xml
[MEDIUM] CVE-2023-6237 (openssl-3.1.4-r3) failed: openssl-3.1.4-r3#L0
trivy-junit-results.xml
[MEDIUM] CVE-2023-26136 (tough-cookie-2.5.0) failed: tough-cookie-2.5.0#L0
trivy-junit-results.xml
[HIGH] DS002 (Dockerfile Security Check) failed: Dockerfile Security Check#L0
trivy-junit-results.xml
[MEDIUM] CVE-2023-26136 (tough-cookie-2.5.0) failed: tough-cookie-2.5.0#L0
trivy-junit-results.xml