# Smoower Index methodology

> The Smoower Index scores developer-facing organizations on public signals only. No surveys, no self-reporting, no private data.

Scores are grouped in two tiers. Foundation covers what a builder finds when they arrive: Code & Polish, Education, AI readiness and Builder experience. Traction covers what happens after: Adoption, Community, Reach and Momentum.

Every org page shows the pillar breakdown, the underlying signals, and the date of the last refresh. Refreshes run continuously, with each org re-scanned on a rolling schedule.

## Pillars

| Pillar | Weight | What it answers | Markdown page |
| --- | --- | --- | --- |
| Code & Polish | ~22% | Are the public repos well-structured, and do real users actually depend on the packages? | https://www.smoower.com/docs/code.md |
| Education | ~18% | Can a developer get from zero to a working integration without asking anyone? | https://www.smoower.com/docs/education.md |
| Community | ~16% | Do outside contributors get answers, and do their changes land? | https://www.smoower.com/docs/community.md |
| Reach and AI readiness | ~18% | When someone asks about this space, does the org come up? Including when an AI answers. | https://www.smoower.com/docs/reach.md |
| Momentum | ~14% | Is the ecosystem moving right now, or coasting? | https://www.smoower.com/docs/momentum.md |
| Builder experience | ~12% | How much surface area is there for a builder to actually build on? | https://www.smoower.com/docs/dx.md |

---

HTML version: https://www.smoower.com/docs
Machine index: https://www.smoower.com/llms.txt · MCP server: https://www.smoower.com/mcp · REST API: https://www.smoower.com/api/v1