wei/git-sync
🔃 A GitHub Action for syncing between two independent repositories using force push
GitHub Actions security score
| wei/git-sync | |
|---|---|
Score | 3/10 |
License | No License |
Maintained | 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0 |
Vulnerabilities | 0 existing vulnerabilities detected |
Docker vulnerabilities | alpine (2 existing vulnerabilities detected) |
Branch protection | branch protection not enabled on development/release branches |
Manual code review | - |
Secure publishing | - |
Signed commits | - |
Automated security tools | - |
Popular | Used by 370 open-source projects |
Security Policy | security policy file not detected |
Networking Behavior of wei/git-sync
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 |
|---|---|
| github.com |  GitHub |
| gitlab.jsc.fz-juelich.de | Unknown |
| codebase.helmholtz.cloud | Unknown |
| gitlab.ebrains.eu | Unknown |