werf
@werf • werf CI/CD tool and related projects. Use this route to separate flagship concentration from portfolio breadth before you treat a publisher as broadly strong.
Portfolio concentration
100%
Top three share
Shows whether the organization is driven by one breakout repo or several visible projects.
Breadth
29 repos
Visible snapshot
10 repositories updated in the last 90 days.
Leading language
Go
Portfolio mix
Go (15), Unknown (9), TypeScript (2)
Average size
38
Stars per repository
Useful for distinguishing one flagship-heavy publisher from a repeatable portfolio.
Updated: 2026-08-10(16d ago)GitHub API fallback29 repositories
100%
of the visible star count comes from this organization's top three repositories.
38
stars per repository in this same snapshot.
Go
is the most common language here, with 10 repositories updated in the last 90 days.
Why this rank
This organization stands out because one flagship repo drives 99% of its visible star count.
Flagship share 99%Breakout repo: nelm
Organization pages work best when you separate portfolio breadth from flagship concentration. In werf's case, the visible top three repositories account for about 100% of total stars in this snapshot, which helps explain whether the organization is known for one breakout project or for a broader repeatable portfolio.
The dominant language mix here is Go (15), Unknown (9), TypeScript (2). That makes this page useful not just for popularity checks, but also for seeing what technical shape an organization's public ecosystem actually has.
Top Repositories
| # | Repository | Language | Stars |
|---|---|---|---|
| 1 | werf/nelm Nelm is a Helm 4 alternative. It is a Kubernetes deployment tool that manages Helm Charts and deploys them to Kubernetes. The Nelm goal is to provide a modern alternative to Helm, with long-standing issues fixed and many new major features introduced. | Go | 1.1K |
| 2 | werf/nelm-operator | Go | 4 |
| 3 | werf/wormatter Comprehensive opinionated formatter for Go | Go | 2 |
| 4 | werf/nelm-chart-ts-sdk TypeScript type definitions for Nelm charts | TypeScript | 1 |
| 5 | werf/3p-buildx Fork of docker/buildx with temporary race-detector fix pending upstream merge. | Go | 0 |
| 6 | werf/buildx-1 Docker CLI plugin for extended build capabilities with BuildKit | 0 | |
| 7 | werf/buildx Docker CLI plugin for extended build capabilities with BuildKit | 0 | |
| 8 | werf/3p-cobra A Commander for modern Go CLI interactions | 0 | |
| 9 | werf/3p-fluxcd-pkg GitOps Toolkit Go SDK | Go | 0 |
| 10 | werf/3p-helm-controller | Go | 0 |
| 11 | werf/nelm-source-controller | Go | 0 |
| 12 | werf/trdl-actions | TypeScript | 0 |
| 13 | werf/common-go | Go | 0 |
| 14 | werf/3p-helm-for-werf-helm | Go | 0 |
| 15 | werf/kubedog-for-werf-helm | Go | 0 |
| 16 | werf/nelm-for-werf-helm | Go | 0 |
| 17 | werf/common-ci | 0 | |
| 18 | werf/3p-buildah A tool that facilitates building OCI images. | 0 | |
| 19 | werf/3p-docker-buildx Docker CLI plugin for extended build capabilities with BuildKit | Go | 0 |
| 20 | werf/3p-deckhouse-cli Command Line Interface to work with Deckhouse Kubernetes Platform | Go | 0 |
| 21 | werf/3p-go-pretty Table-writer and more in golang! | 0 | |
| 22 | werf/3p-storage Container Storage Library | 0 | |
| 23 | werf/3p-oras-go ORAS Go library | 0 | |
| 24 | werf/sample-app | Shell | 0 |
| 25 | werf/3p-helm-plugin-utils Utility functions for use within Helm plugins | Go | 0 |
| 26 | werf/3p-helm-2to3 This is a Helm v3 plugin which migrates and cleans up Helm v2 configuration and releases in-place to Helm v3 | Go | 0 |
| 27 | werf/hello-world-helm-chart | Smarty | 0 |
| 28 | werf/argo-demo | 0 | |
| 29 | werf/ci-cd-with-gitops-demo | Python | 0 |
Next step after the organization read
Open a flagship repository, compare a couple of portfolio leaders, or return to the organization map when you want a broader concentration read.
Learn and methodology
Keep trust-building context reachable, but behind the first data read instead of ahead of it.
How to read this organization snapshot
Total stars are useful as a discovery signal, but they do not tell you whether a team maintains every repository equally. Pair this page with release cadence, maintainer activity, and the flagship concentration shown above before making adoption decisions.
For broader background on GitStar's ranking logic and editorial guidance, see Methodology & Editorial Standards.