step-security/trigger-workflow-and-wait
Secure drop-in replacement for convictional/trigger-workflow-and-wait
Trigger a workflow in another (or same) repository and wait for the job to finish.
GitHub Actions security score comparison
| step-security/trigger-workflow-and-wait | convictional/trigger-workflow-and-wait | |
|---|---|---|
Score | 10/10 | 0/10 |
Pinnable | Yes | Yes |
License | MIT License | MIT License |
Maintained | Maintained by StepSecurity | project is archived |
Vulnerabilities | 0 existing vulnerabilities detected | 0 existing vulnerabilities detected |
Docker vulnerabilities | docker://ghcr.io/step-security/trigger-workflow-and-wait:v1.6.6@sha256:651ae89e1fb66412eb441de19e8c621593b7ae7d6c3e5291d099f6c3a317f6b2 (2 existing vulnerabilities detected) | alpine:3.15.0 (29 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 | 5 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 478 open-source projects |
Security Policy | security policy file detected | security policy file not detected |
Networking Behavior of step-security/trigger-workflow-and-wait
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 |