step-security/semver-utils
Secure drop-in replacement for madhead/semver-utils
One-stop shop for working with semantic versions in your GitHub Actions workflows.
GitHub Actions security score comparison
| step-security/semver-utils | madhead/semver-utils | |
|---|---|---|
Score | 8/10 | 2/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 | 18 existing vulnerabilities detected | 15 existing vulnerabilities detected |
Branch protection | Branch protection is maximal on development and all release branches | branch protection not enabled on development/release branches |
AI analysis | 3 Security findings | Not analyzed yet |
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 131 open-source projects |
Security Policy | security policy file detected | security policy file not detected |
Networking Behavior of step-security/semver-utils
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 |
|---|---|
| prod.app-api.stepsecurity.io | Unknown |