Upgrade to latest ds9 & prx libraries#13
Conversation
Kusari Analysis Results:Caution Flagged Issues Detected While dependency analysis found no actual vulnerabilities in the internal packages from the same organization, the code analysis identified a high-severity policy violation where codecov/codecov-action@v4 is not pinned to a specific commit hash. Although the actual security risk is low given this is a trusted action used only for coverage reporting, the repository's blanket security policy requires all actions to be hash-pinned to prevent supply chain attacks. Security policies must be enforced consistently to maintain security discipline. The fix is straightforward - pin the action to a specific commit hash. Note View full detailed analysis result for more information on the output and the checks that were run. Required Code MitigationsPin the codecov action to a specific commit hash instead of using the v4 tag. This prevents potential supply chain attacks by ensuring the exact version of the action is used consistently.
Required Dependency Mitigations
Found this helpful? Give it a 👍 or 👎 reaction! |
| with: | ||
| fail_ci_if_error: false | ||
| - name: Upload coverage | ||
| uses: codecov/codecov-action@v4 |
There was a problem hiding this comment.
Issue: Pin the codecov action to a specific commit hash instead of using the v4 tag. This prevents potential supply chain attacks by ensuring the exact version of the action is used consistently.
Recommended Code Changes:
uses: codecov/codecov-action@[specific-commit-hash]
No description provided.