werf/nelm
Rank not captured·Top 100·All-time stars·Cached ranking snapshot·
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.
First read
Promising movement, but the picture is still partial
werf/nelm is active enough to inspect further, but the surrounding proof is thinner. Use the source repository and nearby comparisons to decide whether this is rising substance or just short-term visibility.
Visible
1.1K public stars in the current GitStar snapshot.
Needs a narrower context read
Active
Last commit Aug 11, 2026.
Fresh activity
Adopted
Treat stars as discovery context until a linked package appears.
No linked package mapping
Confidence
One or more key signals are partial, so GitStar keeps the interpretation conservative.
Partial snapshot
Snapshot facts
- 1.1K stars
- 28 forks
- Last commit Aug 11, 2026
- Package usage not mapped yet
Compare lens
openshift/origin and werf/werf are the closest comparison targets GitStar found. A side-by-side comparison usually tells you more than a single raw rank.
Signal trail
Trajectory
Read the recent motion first. This block is for deciding whether the repository still looks alive, compounding, or flattening before you trust stars alone.
Daily momentum
Recent momentum is not captured
Weekly momentum
Recent momentum is not captured
Monthly momentum
Recent momentum is not captured
Last commit
Aug 11, 2026
Package reality
No linked npm or PyPI package is mapped for this repository yet, so the page leans more heavily on GitHub-visible popularity and should be read more conservatively.
No linked package signal is expected for this project type, so the read leans more heavily on repository-level public signals.
Hype vs Reality
Insufficient Package Data
Package mapping
No linked package yet
Cross-links
Standalone repo read
Validation note
GitStar can summarize public signals for werf/nelm, but the GitHub repository is still the primary place to confirm release cadence, issue activity, and maintainer intent.
cdci-cdcicdcontinuous-deliverycontinuous-deploymentdeliverydeploydeploymentdevopsgolanghelmhelm-chartiackubernetesnelmwerf
🐙Polyglot
🛡️ Editorial Context
GitStar surfaces public popularity and package signals. These rankings are not endorsements, security reviews, or investment advice.
Why this rank
This repository stands out because it combines fresh update.
Fresh update
📈 Momentum & Adoption Signals
Approximate star trajectory
Reconstructed from current stars and cached daily/weekly/monthly deltas.
Now: 1.1K
Daily momentum
No signal
Weekly momentum
No signal
Monthly momentum
No signal
Signal mix (log-scaled for readability)
Current stars1.1K
🧭 Hype vs Reality
Insufficient Package DataGitStar can see repository momentum, but it does not have a reliable linked package signal yet.
Treat stars and recent movement as discovery context only until npm or PyPI usage is available.
Status
Insufficient Package Data
Package footprint
No linked npm or PyPI usage signal
Method note
This label appears when GitStar cannot find strong enough package telemetry to compare attention against adoption. Compare it against other Go repos before treating stars as a moat.
Related alternative
openshift/origin
Shares the devops category footprint with werf/nelm, so the comparison is closer to a same-problem decision than a same-language coincidence.
Related alternative
werf/werf
Shares the devops category footprint with werf/nelm, so the comparison is closer to a same-problem decision than a same-language coincidence.
Related alternative
erda-project/erda
Shares the devops category footprint with werf/nelm, so the comparison is closer to a same-problem decision than a same-language coincidence.
Related alternative
agola-io/agola
Shares the devops category footprint with werf/nelm, so the comparison is closer to a same-problem decision than a same-language coincidence.
Research links
Cross-links
Compare against related repos
GitStar picked origin + werf as the closest next comparison from the related repository set.
Repo utility
Embed Badge
Preview:
Markdown
[](https://gitstar.space/repo/werf/nelm)HTML
<a href="https://gitstar.space/repo/werf/nelm"><img src="https://gitstar.space/api/badge/werf/nelm" alt="GitStar"></a>Styles:
Wider nearby ecosystem
Go
8.7K starsopenshift/origin
Conformance test suite for OpenShift
Go
4.7K starswerf/werf
A solution for implementing efficient and consistent software delivery to Kubernetes facilitating best practices.
Go
2.7K starserda-project/erda
An enterprise-grade Cloud-Native application platform for Kubernetes.
Go
1.6K starsagola-io/agola
Agola: CI/CD Redefined
Go
1.3K starspipe-cd/pipecd
The One CD for All {applications, platforms, operations}
Go
23.9K starsargoproj/argo-cd
Declarative Continuous Deployment for Kubernetes
Next step after the validation read
Move into a compare preset, organization view, or the heuristic notes once this first fold tells you whether the repo looks visible, active, adopted, and credible enough to keep researching.
Learn and methodology
Keep trust-building context reachable, but behind the first data read instead of ahead of it.
About This Page
This page provides a quick overview of werf/nelm based on GitStar's cached data. The signal chart reconstructs approximate checkpoints from current stars plus cached daily, weekly, and monthly star deltas, so it is best read as directional context rather than as a precise historical audit log.
Want to show your project's ranking? Copy the badge embed code above and add it to your README.