step-security/dynamic-uses
Dynamically resolve and use another GitHub action
GitHub Actions security score
| step-security/dynamic-uses | |
|---|---|
Score | 9/10 |
License | ISC License |
Maintained | Maintained by StepSecurity |
Vulnerabilities | 0 existing vulnerabilities detected |
Branch protection | 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 |
Security Policy | security policy file detected |
Networking Behavior of step-security/dynamic-uses
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.
Popular DestinationUnknown Destination
| Network Destination | Owner |
|---|---|
| api.github.com |  GitHub |