---
title: "werf"
pageType: "tool-profile"
schemaVersion: "1.0"
snapshotId: "tv-20260915-f4c107995a2e"
generatedAt: "2026-09-15T07:02:20.000Z"
canonicalUrl: "https://toolvitals.com/tools/werf/"
jsonUrl: "https://toolvitals.com/api/agent/tools/werf"
indexable: true
---

# werf

A solution for implementing efficient and consistent software delivery to Kubernetes facilitating best practices.

## Decision context

- Status: active
- ToolVitals score: 94/100
- Health score: 95/100
- Shipping score: 94/100
- Score mode: verdict
- Data confidence: 90/100
- Source coverage: 90/100
- Last evidence check: 2026-09-14

## Classification

- Use case: CI/CD (ci-cd)
- Category: DevOps (devops)
- Tool mode: Source-visible project
- Openness: OSI-approved OSS
- License: Apache-2.0
- Tags: open-source, buildah, ci-cd, continuous-delivery, continuous-integration, devops, docker, docker-image, dockerfile, giterminism, gitops, golang, helm, iac, kubernetes, werf

## Public repository signals

- Repository: [werf/werf](https://github.com/werf/werf)
- Stars: 4720 (adoption context only)
- Forks: 239
- Open issues: 28
- Last commit date: 2026-09-14
- Releases in 90 days: 27

## Source receipts

- [Official website](https://werf.io/) — checked 2026-09-14
- [Source repository](https://github.com/werf/werf) — checked 2026-09-14

## Discovery status

- Search indexable: yes
- Reason: sufficient tool evidence

## Interpretation limits

- ToolVitals scores summarize bounded public maintenance, shipping, openness, and evidence signals. They are not user-review ratings.
- GitHub stars and related popularity metrics are adoption context, not quality evidence.
- Missing values mean not collected or not confidently established; they do not mean zero.
- Public signals do not prove security, uptime, support quality, customer satisfaction, or production suitability.
- Verify material decisions against the linked first-party sources and your own requirements.
