step-security/publish-to-bcr
Secure drop-in replacement for bazel-contrib/publish-to-bcr
GitHub release automation for publishing modules to the Bazel Central Registry.
GitHub Actions security score comparison
| step-security/publish-to-bcr | bazel-contrib/publish-to-bcr | |
|---|---|---|
Score | 10/10 | 6/10 |
License | Apache License 2.0 | Apache License 2.0 |
Maintained | Maintained by StepSecurity | 19 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 10 |
Vulnerabilities | 3 existing vulnerabilities detected | 100 existing vulnerabilities detected |
Branch protection | Branch protection is maximal on development and all release branches | Branch protection is 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 253 open-source projects |
Security Policy | security policy file detected | security policy file not detected |
Networking Behavior of step-security/publish-to-bcr
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 |
|---|---|
| github.com |  GitHub |
| api.github.com | GitHub |