aquasecurity/trivy-operator

Kubernetes-native security toolkit

Owned by Aqua Security

View on GitHub ↗Jump to charts ↓

aquasecurity/trivy-operator has 1.5k+ stars and 250+ forks on GitHub, is written in Go, and was last pushed on Oct 13, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 2 minutes ago
Added to GitGenius on October 12th, 2026
Created on May 8th, 2022
Open Issues & Pull Requests: 237 (+0)
GitHub issues: Enabled
Number of forks: 296
Total Stargazers: 1,967 (+0)
Total Subscribers: 8 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 2.8 days
Mean response time: 35.9 days
90th percentile: 80.9 days
Tracked items: 191

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 100% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Work labelled "kind/bug" is answered fastest, typically in about 33 hours, while "kind/feature" waits about 8 days. 56% of tracked open issues have had no activity in three months. Only 9% of issues opened in the past year have been closed.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 116
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 478 days
Stale 30+ days: 102
Stale 90+ days: 81

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 1
Events in 7 days: 3

Top labels

  • kind/bug (144)
  • kind/feature (69)
  • target/kubernetes (18)
  • priority/backlog (16)
  • lifecycle/stale (15)
  • good first issue (6)
  • kind/unsupported (6)
  • triage/support (5)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Trivy Operator is a Kubernetes operator that automates security scanning and compliance checks for workloads and infrastructure running in Kubernetes clusters.

The tool addresses the challenge of continuously monitoring Kubernetes environments for vulnerabilities, misconfigurations, and security risks by embedding security scanning directly into the cluster as a native operator. It works by deploying as a Kubernetes controller that automatically scans container images, Kubernetes manifests, and runtime configurations, then reports findings through Kubernetes custom resources. This approach integrates security assessment into the cluster's native operational model rather than requiring external scanning infrastructure or manual security reviews.

Teams running Kubernetes should adopt this tool if they need automated, ongoing security visibility across their cluster workloads without managing separate scanning infrastructure. It suits organizations that want vulnerability detection and misconfiguration scanning to happen continuously as part of normal cluster operations. The tool is particularly valuable for teams already invested in Kubernetes-native tooling and workflows, since it operates as a standard operator rather than requiring external systems or manual integration points.

The project shows consistent development activity with regular updates addressing both new features and maintenance. The codebase receives ongoing attention to keep pace with evolving Kubernetes APIs and security scanning capabilities. The project maintains active engagement with its user base through issue resolution and feature development. Development work spans multiple areas including operator stability, scanning accuracy, and integration with Kubernetes security patterns.