Below you will find pages that utilize the taxonomy term “Vigilnz”
August 12, 2026
Vigilnz Security Scan
Version updated for https://github.com/Vigilnz/vigilnz-scan-action to version v1.3.1.
This action is used across all versions by ? repositories. Action Type This is a Node action using Node version 20.
Go to the GitHub Marketplace to find the latest changes.
Action Summary The Vigilnz Security Scan Action automates security scanning tasks such as SCA, SBOM, SAST, IAC SCAN, SECRET SCAN, DAST, and CONTAINER SCAN on GitHub repositories. It integrates with Vigilnz’s API to perform these scans and provides outputs directly in the GitHub Actions workflow. The action is easy to use, requiring an API key stored securely in GitHub Secrets and adding a simple step to your workflow YAML file.
August 12, 2026
Vigilnz Security Scan
Version updated for https://github.com/Vigilnz/vigilnz-scan-action to version v1.3.0.
This action is used across all versions by ? repositories. Action Type This is a Node action using Node version 20.
Go to the GitHub Marketplace to find the latest changes.
Action Summary The Vigilnz Security Scan Action automates security scanning for applications and repositories using Vigilnz’s API. It supports multiple scan types including SCA, SBOM, SAST, IAC SCAN, SECRET SCAN, DAST, and CONTAINER SCAN. The action integrates seamlessly with GitHub workflows to help developers detect vulnerabilities during CI/CD pipelines securely and efficiently.
August 7, 2026
Vigilnz Security Scan
Version updated for https://github.com/Vigilnz/vigilnz-scan-action to version v1.2.0.
This action is used across all versions by ? repositories. Action Type This is a Node action using Node version 20.
Go to the GitHub Marketplace to find the latest changes.
Action Summary The Vigilnz Security Scan Action automates security scans for applications and repositories using Vigilnz’s API. It supports SCA, SBOM, SAST, IAC SCAN, SECRET SCAN, DAST, and CONTAINER SCAN. The action makes it easy to integrate security scanning into GitHub workflows by generating an API key, storing it securely in secrets, and adding the action to the workflow configuration.