step-security/super-linter
Secure drop-in replacement for super-linter/super-linter
Combination of multiple linters to run as a GitHub Action or standalone.
GitHub Actions security score comparison
| step-security/super-linter | super-linter/super-linter | |
|---|---|---|
Score | 8/10 | 8/10 |
License | MIT License | MIT License |
Maintained | Maintained by StepSecurity | 30 commit(s) and 9 issue activity found in the last 90 days -- score normalized to 10 |
Vulnerabilities | 34 existing vulnerabilities detected | 24 existing vulnerabilities detected |
Branch protection | Branch protection is maximal on development and all release branches | Branch protection is maximal on development and all release branches |
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 3240 open-source projects |
Security Policy | security policy file detected | security policy file detected |
Networking Behavior of step-security/super-linter
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 |
| mirror.gcr.io | Unknown |
| check.trivy.dev | Unknown |