Portfolio concentration
78%
Top three share
Shows whether the organization is driven by one breakout repo or several visible projects.
Breadth
30 repos
Visible snapshot
4 repositories updated in the last 90 days.
Leading language
Unknown
Portfolio mix
Unknown (11), Go (10), Shell (4)
Average size
13
Stars per repository
Useful for distinguishing one flagship-heavy publisher from a repeatable portfolio.
78%
of the visible star count comes from this organization's top three repositories.
13
stars per repository in this same snapshot.
Unknown
is the most common language here, with 4 repositories updated in the last 90 days.
Why this rank
This organization stands out because its public portfolio is relatively balanced across 30 repositories.
Organization pages work best when you separate portfolio breadth from flagship concentration. In Project Calico's case, the visible top three repositories account for about 78% 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 Unknown (11), Go (10), Shell (4). 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 | projectcalico/vpp-dataplane VPP dataplane implementation for Calico | Go | 170 |
| 2 | projectcalico/node The calico/node container | 102 | |
| 3 | projectcalico/community Calico community content | 41 | |
| 4 | projectcalico/api Calico API | Go | 26 |
| 5 | projectcalico/bpftool Scripts for building bpftool | Makefile | 14 |
| 6 | projectcalico/pod2daemon Secure connections from K8s Pods to local daemons using FlexVolume + Unix Domain Socket | 10 | |
| 7 | projectcalico/networking-calico Calico integration with OpenStack (Neutron) | 7 | |
| 8 | projectcalico/calico-upgrade Data migration tool for Calico upgrades | Python | 7 |
| 9 | projectcalico/containernetworking-plugins Some reference and example networking plugins, maintained by the CNI team. | Go | 4 |
| 10 | projectcalico/spire-demo | Shell | 4 |
| 11 | projectcalico/docker-networking-workshop Workshop covering networking features in Docker swarm mode and Kubernetes in Docker EE | 3 | |
| 12 | projectcalico/tiger-bench Tool for benchmarking kubernetes networking. | Go | 2 |
| 13 | projectcalico/apiserver Kubernetes extension apiserver for Calico REST APIs | 2 | |
| 14 | projectcalico/yaobank Yet Another Online Bank (Demo App) | Makefile | 2 |
| 15 | projectcalico/istio An open platform to connect, manage, and secure microservices. | Go | 2 |
| 16 | projectcalico/scapy-image Docker image for scapy, used in integration tests | Dockerfile | 1 |
| 17 | projectcalico/data-plane-api [READ ONLY MIRROR] Envoy REST/proto API definitions and documentation. | 1 | |
| 18 | projectcalico/packaging Scripts for Debian/RPM packaging of Calico | Shell | 1 |
| 19 | projectcalico/logrus Structured, pluggable logging for Go. | Go | 1 |
| 20 | projectcalico/dockerrun A small go library which wraps the docker CLI | Go | 1 |
| 21 | projectcalico/istio-proxy The Istio proxy components. | C++ | 1 |
| 22 | projectcalico/flannel-cni-plugin | Go | 0 |
| 23 | projectcalico/kubernetes-apiserver Library for writing a Kubernetes-style API server. | 0 | |
| 24 | projectcalico/k8s-client-go Go client for Kubernetes. | 0 | |
| 25 | projectcalico/controller-tools Tools to use with the controller-runtime libraries | 0 | |
| 26 | projectcalico/atomic-wireguard Wireguard kernel module support for Fedora Atomic Host and Silverblue | Shell | 0 |
| 27 | projectcalico/hcsshim Windows - Host Compute Service Shim | 0 | |
| 28 | projectcalico/kind Kubernetes IN Docker - local clusters for testing Kubernetes | Go | 0 |
| 29 | projectcalico/pilot-webhook Istio Pilot Webhook for inserting Envoy filters | Go | 0 |
| 30 | projectcalico/html-proofer-docker HTML validation, made easy | Shell | 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.