step-security/edit-release
Secure drop-in replacement for irongut/editrelease
A GitHub Action for editing an existing release.
GitHub Actions security score comparison
| step-security/edit-release | irongut/editrelease | |
|---|---|---|
Score | 10/10 | 6/10 |
Pinnable | Yes | Yes |
License | MIT License | MIT License |
Maintained | Maintained by StepSecurity | 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0 |
Vulnerabilities | 0 existing vulnerabilities detected | 0 existing vulnerabilities detected |
Docker vulnerabilities | docker://ghcr.io/step-security/edit-release:v1.2.0@sha256:64fe19c5c9dfcb61a19a26f20a1936467e4345fc36e77046664c9d1d477ae226 0 existing vulnerability detected | docker://ghcr.io/irongut/editrelease:v1.2.0 (301 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 |
AI analysis | 4 Security findings | |
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 127 open-source projects |
Security Policy | security policy file detected | security policy file detected |
Networking Behavior of step-security/edit-release
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 |