kyverno/sdk

Kyverno SDK is a Go library that provides programmatic access to Kyverno policy validation and mutation capabilities.

Hosted by Cloud Native Computing Foundation · part of Linux Foundation

View on GitHub ↗Jump to charts ↓

kyverno/sdk has 20+ forks on GitHub, is written in Go, and was last pushed on Oct 16, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 49 minutes ago
Added to GitGenius on October 15th, 2026
Created on January 27th, 2026
Open Issues & Pull Requests: 29 (+0)
GitHub issues: Enabled
Number of forks: 28
Total Stargazers: 1 (+0)
Total Subscribers: 0 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 25.3 hours
Mean response time: 9.5 days
90th percentile: 43.3 days
Tracked items: 7

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 5
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 52 days
Stale 30+ days: 1
Stale 90+ days: 0

Recent activity

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

Top labels

  • bug (1)
  • enhancement (1)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Kyverno SDK is a Go library that provides programmatic access to Kyverno policy validation and mutation capabilities.

The SDK solves the problem of integrating Kyverno's policy engine into applications and tools that need to validate or mutate Kubernetes resources without running a full Kyverno controller. It exposes the core policy evaluation logic through a Go API, allowing developers to embed policy enforcement directly into their workflows, CLIs, or custom tooling. The approach works by packaging Kyverno's validation and mutation engine as a reusable library that can be imported and called from Go applications.

Adoption makes sense for teams building Kubernetes-adjacent tools, testing frameworks, or CI/CD integrations that need to enforce Kyverno policies programmatically. It suits projects where you want policy validation as a library component rather than as a cluster service. This is particularly valuable for developers building policy-as-code tooling, admission webhooks, or policy testing utilities who want to leverage Kyverno's policy language and evaluation engine without the operational overhead of running Kyverno controllers.

The project shows active development with regular commits addressing bug fixes and feature additions. Work spans multiple areas including core policy evaluation logic, test coverage expansion, and dependency management. The maintainers respond to issues and pull requests, indicating ongoing engagement with the user base. Development activity reflects a focus on stability and correctness of the policy evaluation engine rather than rapid feature expansion.