Print logs indicating reasons for build/PR failing V2#1372
Conversation
eranturgeman
commented
Jul 5, 2026
- All tests passed. If this feature is not already covered by the tests, I added new tests.
- This pull request is on the dev branch.
- I used gofmt for formatting the code before submitting the pull request.
- Update documentation about new features / new supported technologies
…-watch-policy-rule-log-v2
…-watch-policy-rule-log-v2
📗 Scan Summary
📦 Vulnerable Dependencies
🔖 Details[ CVE-2021-4435 ] yarn 1.0.0Vulnerability Details
An untrusted search path vulnerability was found in Yarn. When a victim runs certain Yarn commands in a directory with attacker-controlled content, malicious commands could be executed in unexpected ways. [ CVE-2020-8131 ] yarn 1.0.0Vulnerability Details
Arbitrary filesystem write vulnerability in Yarn 1.21.1 and earlier allows attackers to write to any path on the filesystem and potentially lead to arbitrary code execution by forcing the user to install a malicious package. [ CVE-2019-5448 ] yarn 1.0.0Vulnerability Details
Yarn before 1.17.3 is vulnerable to Missing Encryption of Sensitive Data due to HTTP URLs in lockfile causing unencrypted authentication data to be sent over the network. [ CVE-2019-10773 ] yarn 1.0.0Vulnerability Details
In Yarn before 1.21.1, the package install functionality can be abused to generate arbitrary symlinks on the host filesystem by using specially crafted "bin" keys. Existing files could be overwritten depending on the current user permission set. [ CVE-2019-15608 ] yarn 1.0.0Vulnerability Details
The package integrity validation in yarn < 1.19.0 contains a TOCTOU vulnerability where the hash is computed before writing a package to cache. It's not computed again when reading from the cache. This may lead to a cache pollution attack. This issue is fixed in 1.19.0. |


