step-security/publish-unit-test-result-action
Secure drop-in replacement for EnricoMi/publish-unit-test-result-action
GitHub Action to publish unit test results on GitHub
GitHub Actions security score comparison
step-security/publish-unit-test-result-action | EnricoMi/publish-unit-test-result-action | |
---|---|---|
Score | 10/10 | 5/10 |
License | Apache License 2.0 | Apache License 2.0 |
Maintained | Maintained by StepSecurity | 2 commit(s) and 4 issue activity found in the last 90 days -- score normalized to 5 |
Vulnerabilities | 0 existing vulnerabilities detected | 10 existing vulnerabilities detected |
Docker vulnerabilities | docker://ghcr.io/step-security/publish-unit-test-result-action:v2.18.0 (6 existing vulnerabilities detected) | docker://ghcr.io/enricomi/publish-unit-test-result-action:v2.18.0 (10 existing vulnerabilities detected) |
Branch protection | Branch protection is maximal on development and all release branches | branch protection is not maximal on development and all release branches |
Manual code review | Upstream changes are reviewed before merging | - |
Secure publishing | Reproducible builds with SBOM and provenance | - |
Signed commits | All commits are signed | - |
Automated security tools | Findings from tools are triaged and fixed before each change | - |
Popular | Used by StepSecurity enterprise customers | Used by 1064 open-source projects |
Security Policy | security policy file detected | security policy file not detected |
Networking Behavior of step-security/publish-unit-test-result-action
This GitHub Action often makes outbound network calls to these destinations, as gathered from public workflows using the Harden-Runner GitHub Action. Harden-Runner offers network egress filtering and runtime security for both GitHub-hosted and self-hosted runners.
Network Destination | Owner |
---|---|
ghcr.io | ![]() |
api.github.com | ![]() |