step-security/issue-closed-labeler-action
Secure drop-in replacement for rebeccastevens/issue-closed-labeler-action
Conditionally add or remove labels of issues when closed via a PR.
GitHub Actions security score comparison
| step-security/issue-closed-labeler-action | rebeccastevens/issue-closed-labeler-action | |
|---|---|---|
Score | 10/10 | 2/10 |
License | BSD 3-Clause "New" or "Revised" License | BSD 3-Clause "New" or "Revised" License |
Maintained | Maintained by StepSecurity | 1 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0 |
Vulnerabilities | 1 existing vulnerabilities detected | 52 existing vulnerabilities detected |
Branch protection | Branch protection is maximal on development and all release branches | branch protection not enabled on development/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 16 open-source projects |
Security Policy | security policy file detected | security policy file not detected |
Networking Behavior of step-security/issue-closed-labeler-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 |
|---|---|
| api.github.com |  GitHub |