Skip to content

About

Practical, continuously verified open-source DevSecOps tools and a tested CI/CD security pipeline for GitHub Actions, covering SBOM, SAST, SCA, secrets, containers, and signing.

Topics

Resources

Code of conduct

Contributing

Stars

21 stars

Watchers

1 watching

Forks

Repository files navigation

Awesome Security Pipeline

Awesome License: CC0-1.0 Security Baseline

The practical, continuously verified guide to selecting and implementing open-source security tools at every CI/CD pipeline stage.

**78 actively maintained tools · 15 legacy references · status and supply-chain checks refreshed weekly**

Start with a working pipeline, not an empty checklist. The included GitHub Actions baseline runs Gitleaks, Semgrep, OSV-Scanner, Trivy, Syft, and keyless Cosign against a safe demo, retains machine-readable evidence, and passed end to end in 2m21s on GitHub-hosted runners.

Maintenance promise: repository status is checked weekly, license and documentation evidence monthly, and the tested recipe after every relevant change and at least monthly. Classification rules and exceptions are public in the methodology.

Run the tested pipeline → · Choose controls for your project · Browse tools by pipeline stage · Read the verification methodology

Weekly supply-chain report → Every tool in this list is scanned each week at its latest release: dependencies and known vulnerabilities, vulnerable code in the shipped binary, release signature verification, OpenSSF Scorecard, a GitHub Actions workflow audit, CISA KEV and EPSS context, and what changed since last week. Per-advisory pages show which tools match each advisory and which ship the vulnerable code; data is available as JSON, CSV, and Atom feeds. Method.

Security controls from commit through signed package

Start here

If you want to… Start with
See a complete working implementation 10-minute quick start
Understand the architecture and measured implementation findings Technical implementation article
Understand every job, artifact, permission, and failure mode Security demo guide
Review user-visible release changes and verification evidence Changelog
Choose a smaller or more specialized stack Project-type selection matrix
Compare GitHub Actions security tools and permissions Open-source stack comparison
Choose an SBOM generator and validation workflow SBOM tools comparison
See every listed tool's dependencies, known vulnerabilities, and week-over-week changes Weekly supply-chain report
Evaluate why these tools were selected Reference stack decision
Check how projects are selected and classified Curation and verification methodology

10-minute quick start

The fastest safe trial is to run the committed demo in a fork. It requires only a GitHub account and GitHub Actions; it requires no cloud account, custom secret, registry, or deployment.

  1. Fork this repository and enable GitHub Actions in the fork.
  2. Open Actions → Security Baseline → Run workflow and select the default branch.
  3. Confirm the Secrets, SAST, Dependencies, IaC, Build, and Package jobs pass.
  4. Inspect the named scan reports, CycloneDX SBOM, exported image, and immutable digest under Artifacts.
  5. To test keyless signing, push the unchanged workflow to the fork's default branch or a v* tag. Manual and pull-request runs intentionally skip signing.

To adapt the baseline in another repository, copy these paths first, then change the examples/security-demo/app scan and build paths to your application:

.github/workflows/security-baseline.yml
.gitleaks.toml
.semgrep/security-baseline.yml
examples/security-demo/        # replace after the first green run

The default policy fails on detected secrets, configured high-confidence SAST findings, any published dependency vulnerability, and fixed HIGH/CRITICAL configuration or image findings. SARIF upload requires GitHub code scanning support; all reports remain downloadable workflow artifacts. See the demo guide before changing thresholds or permissions.

Choose your baseline

Use the smallest set that covers the artifacts you actually ship. “Regulated” below is a starting architecture, not a compliance claim.

Project type Start with Add when applicable Why
Library Gitleaks, Semgrep, OSV-Scanner Syft for release SBOMs; Cosign for signed release files Protect source and dependencies without container-only stages.
Web application Gitleaks, Semgrep, OSV-Scanner ZAP against a controlled test deployment Combine source/dependency gates with explicit dynamic testing.
Container service Tested baseline: Gitleaks, Semgrep, OSV-Scanner, Trivy, Syft, Cosign Runtime detection such as Falco when operating the service Cover source, image, SBOM, and signed-package risks.
Kubernetes service Container-service baseline Trivy manifest scanning, Kyverno or Gatekeeper admission policy, runtime detection Separate build-time evidence from cluster admission and runtime controls.
Regulated project Relevant baseline above with retained SARIF, SBOM, digest, and signature Organization-specific policy, approvals, provenance, and evidence retention Produce reviewable evidence while leaving control mapping to the applicable framework.

Contents


Tool catalog

Entries are organized by where they operate in a delivery pipeline. Status reflects repository activity, not security effectiveness; stars indicate adoption, not quality. Multi-purpose tools may appear in more than one category with a category-specific description.

Status: 🟢 Active (commit in the last 6 months) · 🟡 Stale (6–12 months) · 🔴 Unmaintained (over 12 months) · ⚪ Archived. Unmaintained and archived tools move to Legacy automatically and return when they are active again. Scorecard (OpenSSF, out of 10) and Release (whether the Linux release file's signature, provenance, or attestation verifies) come from the weekly supply-chain report; select a Scorecard value for the tool's full report. Every column is refreshed weekly from each tool's file in tools/.

Pre-commit & Secrets Detection

Catch secrets and credentials before they enter your repository.

ToolWhat it doesStatus★ScorecardRelease
detect-secretsPrevent secrets from entering codebases🟡 Stale
Apr 2026
4.7k3.5—
gitleaksDetect and prevent secrets in git repos🟢 Active
Oct 2026
30.6kreportChecksums
pre-commitManage multi-language pre-commit hooks🟢 Active
Oct 2026
15.7k4.5—
talismanDetect secrets with pre-push and pre-commit hooks🟡 Stale
Nov 2025
2.1k3.3Checksums
trufflehogFind credentials in git history and live systems🟢 Active
Nov 2026
28.8k7.9✓ Verified

SBOM Generation

Generate Software Bill of Materials for supply chain visibility.

ToolWhat it doesStatus★ScorecardRelease
cdxgenCreate CycloneDX SBOMs for various languages🟢 Active
Nov 2026
1.1kreportChecksums
cyclonedx-cliInspect, convert, and merge CycloneDX SBOMs🟢 Active
Jul 2026
552report—
sbom-toolGenerate SBOMs for build artifacts and source repositories🟢 Active
Sep 2026
2.1kreport—
sbomlyzeCompare SBOMs to detect supply-chain drift Maintained by this list's maintainer.🟢 Active
Nov 2026
267.9✓ Verified
syftGenerate SBOMs from container images and filesystems🟢 Active
Nov 2026
9.8k8.7✓ Verified

Artifact Signing & Verification

Sign and verify container images and artifacts for supply chain security.

ToolWhat it doesStatus★ScorecardRelease
cosignSign and verify container images🟢 Active
Oct 2026
6.4k8.2✓ Verified
notationSign and verify OCI artifacts with Notary Project specifications🟢 Active
Oct 2026
5026.5Checksums
rekorRecord signed artifacts in a tamper-resistant transparency log🟢 Active
Oct 2026
1.2k8.6✓ Verified

Supply Chain Compliance

Audit and verify supply chain security against industry benchmarks.

ToolWhat it doesStatus★ScorecardRelease
in-totoProtect software supply-chain integrity with signed metadata🟢 Active
Aug 2026
1.1k6.5—
scorecardMeasure open-source project security practices with OpenSSF checks🟢 Active
Oct 2026
5.8k8.6✓ Verified
slsa-verifierVerify SLSA provenance for supply chain security🟢 Active
Aug 2026
352report✓ Verified

Software Composition Analysis (SCA)

Scan dependencies for known vulnerabilities.

ToolWhat it doesStatus★ScorecardRelease
bomberScan SBOMs for vulnerabilities🟡 Stale
Feb 2026
629reportChecksums
dependency-trackTrack components and analyze dependency risk from SBOMs🟢 Active
Nov 2026
4.4k7.5—
grypeScan filesystems and SBOMs for dependency vulnerabilities🟢 Active
Oct 2026
13.2k7.9✓ Verified
osv-scannerScan dependencies for vulnerabilities in the OSV database🟢 Active
Oct 2026
11.3k8.6✓ Verified
safe-chainBlock malicious packages during npm/pip install🟢 Active
Oct 2026
1.8k4.5✓ Verified
snyk-cliFind and fix vulnerabilities in dependencies🟢 Active
Oct 2026
5.7kreportChecksums
trivyScan operating-system and language dependencies for vulnerabilities🟢 Active
Oct 2026
38.9k7.1✓ Verified
vetEnforce dependency policies and report supply-chain risks🟢 Active
Nov 2026
1.1k7.4✓ Verified

Static Application Security Testing (SAST)

Analyze source code for security vulnerabilities.

Multi-language

Tools that support multiple programming languages.

ToolWhat it doesStatus★ScorecardRelease
bearerTrace sensitive data flows and detect security risks in code🟢 Active
Oct 2026
2.8k6.3Checksums
codeqlAnalyze code semantically with GitHub's query engine🟢 Active
Oct 2026
10.3k5.8—
semgrepScan source code with multi-language static-analysis rules🟢 Active
Oct 2026
17.4kreport—
sonarqubeInspect code continuously for quality and security issues🟢 Active
Oct 2026
11.1k4.9—
spotbugsFind bug patterns in Java bytecode🟢 Active
Nov 2026
4k4.6—

Language-specific

Specialized tools for individual programming languages.

Python

ToolWhat it doesStatus★ScorecardRelease
banditFind common security issues in Python code🟢 Active
Oct 2026
8.4k5.8—
safetyCheck Python dependencies for vulnerabilities🟢 Active
Sep 2026
2k4.7—

JavaScript/Node.js

ToolWhat it doesStatus★ScorecardRelease
eslint-plugin-securityDetect security patterns in Node.js with ESLint rules🟢 Active
Oct 2026
2.4kreport—
njsscanAnalyze Node.js applications with semantic SAST rules🟢 Active
Oct 2026
4585.5—

Go

ToolWhat it doesStatus★ScorecardRelease
gosecFind security issues in Go source code🟢 Active
Oct 2026
9k6.6✓ Verified
govulncheckReport reachable Go vulnerabilities in source and binaries🟢 Active
Oct 2026
5323.7—

Ruby

ToolWhat it doesStatus★ScorecardRelease
brakemanScan Ruby on Rails applications with static analysis🟢 Active
Oct 2026
7.3k6.0—

PHP

ToolWhat it doesStatus★ScorecardRelease
phpstanAnalyze PHP code without running it🟢 Active
Nov 2026
14.1k4.8—
psalmAnalyze PHP code for type and security issues🟢 Active
Nov 2026
5.9k4.7—

Rust

ToolWhat it doesStatus★ScorecardRelease
cargo-auditAudit Cargo.lock for crates with security vulnerabilities🟢 Active
Oct 2026
2kreport—

Infrastructure as Code Security

Scan infrastructure configurations for security misconfigurations.

ToolWhat it doesStatus★ScorecardRelease
cfn-lintLint AWS CloudFormation templates with security rules🟢 Active
Oct 2026
2.6k6.0—
checkovScan cloud infrastructure configurations🟢 Active
Oct 2026
9.1kreport—
kicsFind security vulnerabilities and compliance issues in IaC🟢 Active
Oct 2026
2.7kreport—
snyk-cliScan infrastructure as code for security issues🟢 Active
Oct 2026
5.7kreportChecksums
trivyScan Terraform, CloudFormation, and other IaC for misconfigurations🟢 Active
Oct 2026
38.9k7.1✓ Verified
zizmorAnalyze GitHub Actions workflows for security issues🟢 Active
Oct 2026
6.9kreport✓ Verified

Container Security

Secure container images and runtime environments.

Image Scanning

Scan container images for vulnerabilities before deployment.

ToolWhat it doesStatus★ScorecardRelease
clairAnalyze container images for known vulnerabilities🟢 Active
Oct 2026
11.1k5.0—
diveInspect image layers and contents; it does not scan vulnerability databases🟢 Active
Oct 2026
54.7k3.4Checksums
docker-bench-securityCheck Docker deployment against CIS benchmarks🟢 Active
Jun 2026
9.7k6.7—
dockleLint container images for security best practices🟢 Active
Jul 2026
3.3k4.1Checksums
grypeScan container images for operating-system and library vulnerabilities🟢 Active
Oct 2026
13.2k7.9✓ Verified
hadolintLint Dockerfiles for security and build best practices🟢 Active
Oct 2026
12.5k4.7✓ Verified
trivyScan container images for operating-system and library vulnerabilities🟢 Active
Oct 2026
38.9k7.1✓ Verified

Runtime Security

Monitor and protect containers at runtime.

ToolWhat it doesStatus★ScorecardRelease
falcoDetect runtime threats in cloud-native environments🟢 Active
Oct 2026
9.5k7.5—
sysdig-inspectVisualize system calls and analyze containers🟢 Active
Jul 2026
1kreport—
tetragonObserve and enforce runtime security with eBPF🟢 Active
Oct 2026
5.1kreport—
traceeTrace Linux runtime activity and security events with eBPF🟢 Active
Sep 2026
4.7k7.0Checksums

Kubernetes Security

Secure Kubernetes clusters, manifests, and workloads.

ToolWhat it doesStatus★ScorecardRelease
kube-benchCheck Kubernetes against CIS benchmarks🟢 Active
Oct 2026
8.2k5.8Checksums
kube-linterAnalyze Kubernetes YAML and Helm charts before deployment🟢 Active
Oct 2026
3.5k7.4Signed
kubescapeAnalyze Kubernetes security risk and configuration compliance🟢 Active
Oct 2026
11.8k7.6✓ Verified
KubeStellar ConsoleView security signals across multiple Kubernetes clusters🟢 Active
Nov 2026
152report✓ Verified
kyvernoEnforce policies with Kubernetes-native resources🟢 Active
Nov 2026
8.3k7.8✓ Verified
polarisValidate Kubernetes best practices and policies🟢 Active
Oct 2026
3.4k5.1Signed
trivy-operatorGenerate Kubernetes-native security reports🟢 Active
Oct 2026
2k7.5✓ Verified

Policy as Code

Define and enforce security policies as code across your infrastructure.

ToolWhat it doesStatus★ScorecardRelease
conftestTest configuration files against OPA policies🟢 Active
Oct 2026
3.3k7.2✓ Verified
gatekeeperEnforce OPA policies through Kubernetes admission control🟢 Active
Oct 2026
4.3kreport✓ Verified
opaEvaluate policy as code across application and infrastructure systems🟢 Active
Nov 2026
12.4k8.2✓ Verified

Secret Management

Securely manage and distribute secrets in Kubernetes and GitOps workflows.

ToolWhat it doesStatus★ScorecardRelease
external-secretsSync secrets from AWS/Vault/Azure into Kubernetes🟢 Active
Oct 2026
6.9k8.3—
infisicalManage application secrets with automation integrations🟢 Active
Nov 2026
30.2k6.9—
sealed-secretsEncrypt secrets locally, decrypt only in cluster🟢 Active
Oct 2026
9.3k6.8Signed
sopsEncrypt structured files while preserving editor workflows🟢 Active
Oct 2026
23.6kreport✓ Verified
vaultManage secrets, encryption, and privileged access🟢 Active
Oct 2026
36.5k6.5—

API & Dynamic Testing (DAST)

Test running applications for vulnerabilities.

ToolWhat it doesStatus★ScorecardRelease
Dark-MoonAutonomous AI penetration testing platform that exercises running web, API, Active Directory and Kubernetes targets with proof of exploitation🟢 Active
Oct 2026
1.2k3.8—
niktoScan web servers for dangerous files and known vulnerabilities🟢 Active
Aug 2026
10.8k3.8—
nucleiScan applications and infrastructure with customizable templates🟢 Active
Oct 2026
32.5k6.8Checksums
sqlmapDetect and validate SQL injection vulnerabilities🟢 Active
Oct 2026
38.8k4.9—
wapitiScan web applications for vulnerabilities with black-box testing🟢 Active
Oct 2026
1.9kreport—
zapScan web applications dynamically with OWASP ZAP🟢 Active
Nov 2026
16.1k6.8—

Cloud Security

Assess and audit cloud infrastructure security posture.

ToolWhat it doesStatus★ScorecardRelease
cartographyMap infrastructure relationships and attack surface🟢 Active
Nov 2026
4.2k8.1—
cloudqueryInventory cloud assets and analyze them with SQL🟢 Active
Nov 2026
6.6k6.0Checksums
cloudsplainingAssess AWS IAM policies for risky permissions🟢 Active
Oct 2026
2.3k5.7—
prowlerAssess AWS, Azure, and GCP security configurations🟢 Active
Oct 2026
15.2kreport—
steampipeQuery cloud resources using SQL🟢 Active
Nov 2026
8k6.8✓ Verified

Legacy and Reference Tools

These projects are kept for migration research and historical context, not recommended for new adoption. They are listed here because their repositories are archived or have had no commit for over 12 months. Prefer the alternative noted beside an entry or a maintained tool from the matching category above.

Pre-commit & Secrets Detection

ToolWhat it didStatus★Use instead
git-secretsPrevent committing AWS credentials and secrets🔴 Unmaintained
Sep 2025
13.4k—
whispersIdentify hardcoded secrets in static code analysis⚪ Archived
Oct 2021
506—

SBOM Generation

ToolWhat it didStatus★Use instead
spdx-sbom-generatorGenerate SPDX format SBOMs from source code⚪ Archived
Jan 2025
427—
ternAnalyze container images for software composition🔴 Unmaintained
Dec 2023
1k—

Supply Chain Compliance

ToolWhat it didStatus★Use instead
chain-benchAudit supply chain against CIS benchmarks🔴 Unmaintained
Jul 2024
772—

Static Application Security Testing (SAST) › Multi-language

ToolWhat it didStatus★Use instead
horusecAnalyze source code across multiple languages🔴 Unmaintained
Aug 2023
1.3k—

Static Application Security Testing (SAST) › Language-specific › Python

ToolWhat it didStatus★Use instead
pyre-checkAnalyze Python types and selected security properties⚪ Archived
Jun 2026
7.2k—

Infrastructure as Code Security

ToolWhat it didStatus★Use instead
terrascanDetect compliance and security violations in IaC⚪ Archived
Nov 2025
5.2k—
tfsecScan Terraform code for security issues🔴 Unmaintained
May 2025
7.1k—

Container Security › Image Scanning

ToolWhat it didStatus★Use instead
anchore-engineAnalyze containers and evaluate image policies⚪ Archived
Jan 2023
1.6ksyft, grype

Kubernetes Security

ToolWhat it didStatus★Use instead
kube-hunterHunt for security weaknesses in Kubernetes clusters🔴 Unmaintained
Mar 2024
5.1k—
kubiscanScan Kubernetes RBAC for risky permissions🔴 Unmaintained
May 2025
1.4k—

Policy as Code

ToolWhat it didStatus★Use instead
datreePrevent Kubernetes misconfigurations⚪ Archived
Aug 2023
6.3k—

API & Dynamic Testing (DAST)

ToolWhat it didStatus★Use instead
arachniScan web applications for security issues⚪ Archived
Apr 2026
4kzap, nuclei

Cloud Security

ToolWhat it didStatus★Use instead
ScoutSuiteAudit security configurations across multiple cloud providers🔴 Unmaintained
May 2024
7.9k—

Contributing

Contributions are welcome! Please read the contribution guidelines first.

To add a tool, add one JSON file in tools/; the catalog above is generated from those files. Before submitting:

  • Repository must be at least 1 month old (anti-spam requirement)
  • Repository must have at least 5 stars
  • Tool must have been updated within the last 12 months
  • You must disclose any affiliation with the tool

See CONTRIBUTING.md for full details.

License

CC0

To the extent possible under law, the contributors have waived all copyright and related or neighboring rights to this work.

About

Practical, continuously verified open-source DevSecOps tools and a tested CI/CD security pipeline for GitHub Actions, covering SBOM, SAST, SCA, secrets, containers, and signing.

Topics

Resources

Code of conduct

Contributing

Stars

21 stars

Watchers

1 watching

Forks

Releases

Contributors

Languages