convictional/trigger-workflow-and-wait
Trigger a workflow in another (or same) repository and wait for the job to finish.
GitHub Actions security score
| convictional/trigger-workflow-and-wait | |
|---|---|
Score | 0/10 |
Pinnable | Yes |
License | MIT License |
Maintained | project is archived |
Vulnerabilities | 0 existing vulnerabilities detected |
Docker vulnerabilities | alpine:3.15.0 (29 existing vulnerabilities detected) |
Branch protection | branch protection is not maximal on development and all release branches |
AI analysis | 5 Security findings |
Manual code review | - |
Secure publishing | - |
Signed commits | - |
Automated security tools | - |
Popular | Used by 471 open-source projects |
Security Policy | security policy file not detected |
Networking Behavior of convictional/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.
Popular DestinationUnknown Destination
| Network Destination | Owner |
|---|---|
| api.github.com |  GitHub |
| warpbuild-prod-runner-telemetry.s3.us-east-1.amazonaws.com | Unknown |
| ec2messages.eu-central-1.amazonaws.com | Unknown |
| logs.eu-central-1.amazonaws.com | Unknown |
| ssm.eu-central-1.amazonaws.com | Unknown |
| ts01-lanner-lion.cloudsink.net | Unknown |
| lfodown01-lanner-lion.cloudsink.net | Unknown |