PipeCD
@pipe-cd • The One CD for All {applications, platforms, operations}. Use this route to separate flagship concentration from portfolio breadth before you treat a publisher as broadly strong.
Portfolio concentration
94%
Top three share
Shows whether the organization is driven by one breakout repo or several visible projects.
Breadth
16 repos
Visible snapshot
4 repositories updated in the last 90 days.
Leading language
Go
Portfolio mix
Go (4), Unknown (4), HCL (3)
Average size
95
Stars per repository
Useful for distinguishing one flagship-heavy publisher from a repeatable portfolio.
Updated: 2026-08-26(just now)GitHub API fallback16 repositories
94%
of the visible star count comes from this organization's top three repositories.
95
stars per repository in this same snapshot.
Go
is the most common language here, with 4 repositories updated in the last 90 days.
Why this rank
This organization stands out because one flagship repo drives 89% of its visible star count.
Flagship share 89%Breakout repo: pipecd
Organization pages work best when you separate portfolio breadth from flagship concentration. In PipeCD's case, the visible top three repositories account for about 94% 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 (4), Unknown (4), HCL (3). 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 | pipe-cd/pipecd The One CD for All {applications, platforms, operations} | Go | 1.3K |
| 2 | pipe-cd/actions-gh-release An action that enables operating GitHub release via pull request. | Dockerfile | 37 |
| 3 | pipe-cd/examples Examples to demonstrate how to use PipeCD | HCL | 35 |
| 4 | pipe-cd/tutorial Tutorial for the beginners in 30m-1h | HCL | 24 |
| 5 | pipe-cd/actions-plan-preview An action that comments PipeCD's PlanPreview result on GitHub pull request | Dockerfile | 17 |
| 6 | pipe-cd/actions-event-register A GitHub action for registering Events to PipeCD | 14 | |
| 7 | pipe-cd/community-plugins Collection of PipeCD plugins developed by the community. | Go | 9 |
| 8 | pipe-cd/terraform-provider-pipecd | Go | 9 |
| 9 | pipe-cd/orb-pipecd CircleCI Orb for interacting with PipeCD | 7 | |
| 10 | pipe-cd/docs-mcp-server A local MCP server for searching official PipeCD docs. | TypeScript | 6 |
| 11 | pipe-cd/piped-plugin-sdk-go | Go | 4 |
| 12 | pipe-cd/homebrew-tap | Ruby | 2 |
| 13 | pipe-cd/demo Demonstrations of PipeCD for the beginners | 1 | |
| 14 | pipe-cd/control-plane-aws-ecs-terraform-demo Example of installing Control Plane on ECS by Terraform | HCL | 1 |
| 15 | pipe-cd/piped-images | 0 | |
| 16 | pipe-cd/asdf-pipectl | Shell | 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.