Real figures from the TDK CLI GitHub repository as of October 18, 2026: stars, forks, releases, merged pull requests, open and closed issues, and contributors. What the numbers show, and what they don't.
Most project posts quote numbers without saying where they came from. These are read directly from the tdk-cli-core repository on GitHub on October 18, 2026, using the GitHub CLI. They will have changed by the time you read this, so check the repo for current values.
The snapshot
| Measure | Value |
|---|---|
| Stars | 21 |
| Forks | 25 |
| Watchers | 1 |
| Contributors | 29 |
| Releases published | 51 |
| Latest release | v1.3.183, published October 17, 2026 |
| Merged pull requests | 857 |
| Open pull requests | 9 |
| Open issues | 306 |
| Closed issues | 338 |
Open issues labelled hacktoberfest
|
171 |
| Primary language | TypeScript |
| License | MIT |
What the numbers say
Releases are frequent. Fifty-one releases, with the latest a patch release on the 17th. A small, steady release rhythm is a sign the project ships often rather than in large batches.
Work gets merged. Eight hundred and fifty-seven merged pull requests against nine open ones means most proposed changes land. The open count is small enough to review.
Issues are a backlog and a menu. Roughly equal numbers of open and closed issues, 306 and 338, show that the tracker is both active and long. Of the open ones, 171 carry the hacktoberfest label, which makes the tracker a practical place to pick work.
The community is small but present. Twenty-nine contributors, twenty-five forks, and twenty-one stars. These are modest numbers. The stars in particular are a weak signal of use, because many people who run a tool never star it.
What the numbers don't say
Stars and forks do not measure how many teams run TDK in production, and the repository does not list adopters in these figures. The repo's own adopters file is the place to look for named users, and the adoption issue asks teams to add themselves.
Contributor count is not the same as the number of people who have had work merged. The Hall of Fame issue, #602, tracks merged contributors separately, and it lists 24 at the time of my check.
How to read this
Use the numbers to judge the project's pace, not its reach. A tool with many merged changes and frequent releases is actively maintained. A tool with few stars may still be the right fit for your team, and the way to know is to try it.
Reproducing the numbers
Anyone can check these values with the GitHub CLI:
gh repo view tdk-landscape/tdk-cli-core --json stargazerCount,forkCount
gh issue list -R tdk-landscape/tdk-cli-core --state open --limit 1000 --json number -q 'length'
gh pr list -R tdk-landscape/tdk-cli-core --state merged --limit 1000 --json number -q 'length'
Keep the --limit high enough for the count you expect, or the result will be capped.
Summary
As of October 18, 2026, TDK CLI has 21 stars, 25 forks, 51 releases, 857 merged pull requests, and 306 open issues, of which 171 are labelled for Hacktoberfest. The numbers show an actively merged, frequently released project with a small community. They do not show how widely it is used, which is a question for the adopters list rather than the star count.
Top comments (1)
TDK CLI describes each service in a service.json file, generates the Docker, routing, and Tilt files from it, and starts the whole stack with tdk up. Three features help with fragility:
tdk doctor --json checks whether the machine can run the stack, including whether a container runtime is reachable.
tdk up main --dry-run shows the plan, the ports, and the start order without starting anything.
Drift checks compare the generated files with saved snapshots before startup, so a hand-edited Dockerfile or Tiltfile blocks the start and names the file.
It is for local development. Production deployment stays with tools such as Helm, Argo CD, or Kustomize. It also supports an MCP server, tdk mcp, if you want an agent to start the stack and read its readiness directly.