Below you will find pages that utilize the taxonomy term “Wraith-Security”
August 6, 2026
Legion Runner
Version updated for https://github.com/Wraith-security/Legion_runner to version v1.0.58.
This action is used across all versions by 8 repositories. Action Type This is a Node action using Node version 24.
Go to the GitHub Marketplace to find the latest changes.
Action Summary Legion Runner is an open-source action designed to protect CI/CD pipelines from supply chain attacks by monitoring and blocking outbound connections from GitHub Actions jobs. It records every outbound connection, names the process behind it, and blocks any unauthorized destinations, ensuring that only allowed services can be accessed. The Action has no dependencies and runs on pure Node built-ins with optional eBPF capture and file-integrity helpers for enhanced security features.
August 5, 2026
Legion Runner
Version updated for https://github.com/Wraith-security/Legion_runner to version v1.0.57.
This action is used across all versions by 8 repositories. Action Type This is a Node action using Node version 24.
Go to the GitHub Marketplace to find the latest changes.
Action Summary Legion Runner is an open-source GitHub Action that strengthens CI security by monitoring and blocking outbound connections from jobs. It records connection details, names processes, and checks for file tampering, enhancing defense against supply chain attacks without leaving the runner environment. The action uses Rust for its core components and can be integrated into any job, including hosted runners.
August 4, 2026
Legion Runner
Version updated for https://github.com/Wraith-security/Legion_runner to version v1.0.55.
This action is used across all versions by 8 repositories. Action Type This is a Node action using Node version 24.
Go to the GitHub Marketplace to find the latest changes.
Action Summary Legion Runner is an open-source action designed to protect GitHub Actions jobs against supply chain attacks by monitoring and blocking outbound connections based on predefined allowlists. It records process names, fingerprints credentials and configuration files, and runs without dependencies or sending data to external services. The Action can be integrated as the first step of a job and provides modes for logging and blocking outbound traffic.