Portfolio concentration
99%
Top three share
Shows whether the organization is driven by one breakout repo or several visible projects.
Breadth
30 repos
Visible snapshot
16 repositories updated in the last 90 days.
Leading language
Shell
Portfolio mix
Shell (7), Go (6), Unknown (5)
Average size
34
Stars per repository
Useful for distinguishing one flagship-heavy publisher from a repeatable portfolio.
99%
of the visible star count comes from this organization's top three repositories.
34
stars per repository in this same snapshot.
Shell
is the most common language here, with 16 repositories updated in the last 90 days.
Why this rank
This organization stands out because one flagship repo drives 98% of its visible star count.
Organization pages work best when you separate portfolio breadth from flagship concentration. In vCluster's case, the visible top three repositories account for about 99% 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 Shell (7), Go (6), Unknown (5). That makes this page useful not just for popularity checks, but also for seeing what technical shape an organization's public ecosystem actually has.
| # | Repository | Language | Stars |
|---|---|---|---|
| 1 | loft-sh/vind vCluster in Docker (vind) is KinD (Kubernetes in Docker) alternative with additional features. For source code, see loft-sh/vcluster repo linked below. | 993 | |
| 2 | loft-sh/certified-stacks | HCL | 8 |
| 3 | loft-sh/vcluster-candy Cluster Aware Node-local DNS proxY | Go | 2 |
| 4 | loft-sh/vcluster-bare-metal-with-kubevirt | Makefile | 2 |
| 5 | loft-sh/setup-vind GitHub Action to provision Kubernetes clusters via vCluster Docker driver (vind) | TypeScript | 2 |
| 6 | loft-sh/vcluster-auto-nodes-gcp Terraform modules for Auto Nodes on GCP | HCL | 2 |
| 7 | loft-sh/os-images Public OS Images | Makefile | 1 |
| 8 | loft-sh/vm-container Lightweight container that mimics a full operating system including systemd & cloud-init | Shell | 1 |
| 9 | loft-sh/vcluster-templates | 1 | |
| 10 | loft-sh/vcluster-auto-nodes-azure Terraform modules for Auto Nodes on Azure | HCL | 1 |
| 11 | loft-sh/vcluster-auto-nodes-aws Terraform modules for Auto Nodes on AWS | HCL | 1 |
| 12 | loft-sh/karpenter Karpenter is a Kubernetes Node Autoscaler built for flexibility, performance, and simplicity. | Go | 1 |
| 13 | loft-sh/kubernetes Kubernetes in a single container | Shell | 1 |
| 14 | loft-sh/baremetal-operator Bare metal host provisioning integration for Kubernetes | 0 | |
| 15 | loft-sh/vcluster-control-plane-load-testing vCluster Control Plane Load Test Framework with Simulated Nodes | Shell | 0 |
| 16 | loft-sh/terraform-aws-vcluster-standalone Terraform Script to deploy vCluster Standalon on AWS EC2 | HCL | 0 |
| 17 | loft-sh/vcluster-selinux SELinux policy RPM for vCluster | Shell | 0 |
| 18 | loft-sh/bridge-operator Bridge-operator manages linux bridge in Kubernetes cluster node. | Go | 0 |
| 19 | loft-sh/kubevirtbmc IPMI/Redfish service for KubeVirt virtual machines | 0 | |
| 20 | loft-sh/docs-forwardport-action GitHub Action to forwardport documentation changes from versioned folders to main folders in Docusaurus projects | TypeScript | 0 |
| 21 | loft-sh/vcluster-gcp-deployer | Mustache | 0 |
| 22 | loft-sh/api-example | Go | 0 |
| 23 | loft-sh/vcluster-attach-detach Script to simplify detaching and later attaching vCluster resources | Shell | 0 |
| 24 | loft-sh/image Work with containers' images | Go | 0 |
| 25 | loft-sh/bcm-scripts | Shell | 0 |
| 26 | loft-sh/setup-kind kind (Kubernetes in Docker) GitHub Action | TypeScript | 0 |
| 27 | loft-sh/magpie Hoards kubernetes events. Runs within a parent process. | Go | 0 |
| 28 | loft-sh/init-node Easy script to init a node before joining via Kubeadm | Shell | 0 |
| 29 | loft-sh/docker-credential-acr-env | 0 | |
| 30 | loft-sh/docs-backport-action Backport action for vcluster-docs | TypeScript | 0 |
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.