# kptdev/kpt

Automate Kubernetes Configuration Editing

Repository: https://github.com/kptdev/kpt
Canonical: https://ross.abutalabs.com/products/kpt
Homepage: https://kpt.dev
Language: Go
License: Apache-2.0
License Family: permissive
Topics: krm, kpt, configuration-management, gitops, kubernetes, kubectl, kustomize, containers, schema, openapi, cli, deployment, packaging-tool, customization, validation, policy-as-code, config-as-data, shift-left
Last push: 2026-08-26T11:33:12+00:00

## Health v2 (maintenance only)
Score: 98/100 (v2, computed 2026-09-03T02:20:16.233290+00:00)
- activity 99, release rhythm 97, longevity 100
- inputs: {"age_days": 2543, "days_push": 7, "days_rel": 20, "gap_med": 24, "n_releases_24m": 14}
- flags: none
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 1890, forks 262 (observed 2026-08-28T04:05:49.564469+00:00)

## What it is
kpt is a package-centric CLI toolchain for authoring, customizing, validating, and deploying Kubernetes configuration as declarative data (KRM YAML/JSON). It supports WYSIWYG in-place editing, package upgrades from upstream sources, GitOps delivery, and includes Porch for Kubernetes-native package orchestration.

## Use cases
- manage kubernetes configuration as data at scale
- customize and upgrade kustomize-style config packages
- apply kubernetes resources with pruning and aggregated status
- run gitops workflows for krm packages
- validate kubernetes manifests against openapi schemas
- author and transform krm yaml packages with krm functions
- orchestrate config package lifecycle in a kubernetes cluster with porch

## When to choose
- you manage many kubernetes clusters or platforms with declarative config packages
- you want in-place WYSIWYG config editing instead of out-of-place overlays
- you need upstream package upgrades that preserve downstream modifications
- you want gitops delivery with resource inventory, pruning, and status aggregation

## When to avoid
- you only need simple kustomize overlays without package management
- your team prefers templating-based config generation like helm
- you don't use kubernetes or KRM-based infrastructure
- you want a fully turnkey managed platform rather than a CLI toolchain

## Facets
- artifact type: cli-tool
- maturity: active
- function: configuration-management, deployment, cli, developer-tools, workflow-automation
- domain: infrastructure-as-code, cloud-computing, self-hosted
- platform: cli, go, cross-platform
- tags: kubernetes, krm, gitops, config-as-data, kustomize, policy-as-code, package-management, cncf-sandbox, porch, yaml, openapi-schema, shift-left, devops, containers, automation, linux, macos, docker

## Member repositories
- kptdev/kpt (main) score 98

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:05:49.564469+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-30T03:13:02.128807+00:00, confidence not recorded.
  - readme: https://github.com/kptdev/kpt (fetched 2026-08-28T04:05:49.564469+00:00, sha e5942f491a8a)
  - homepage: https://kpt.dev (fetched 2026-08-29T10:52:25.046451+00:00, sha 600548655183)
  - site_page: https://porch.kpt.dev/docs (fetched 2026-08-29T10:52:25.055544+00:00, sha 0c18c8a1d8e6)
  - site_page: https://kpt.dev/installation/kpt-cli (fetched 2026-08-29T10:52:25.057394+00:00, sha af1f0fae4502)
  - site_page: https://kpt.dev/installation (fetched 2026-08-29T10:52:25.061000+00:00, sha aaa4b3f18961)
  - site_page: https://kpt.dev/faq (fetched 2026-08-29T10:52:25.059350+00:00, sha 0473cba0d0ce)
- Data as of 2026-08-30T08:39:29.467469+00:00.