iii
@iii-hq • Open source projects from iii-hq. Use this route to separate flagship concentration from portfolio breadth before you treat a publisher as broadly strong.
Portfolio concentration
100%
Top three share
Shows whether the organization is driven by one breakout repo or several visible projects.
Breadth
14 repos
Visible snapshot
7 repositories updated in the last 90 days.
Leading language
Rust
Portfolio mix
Rust (6), Unknown (3), TypeScript (3)
Average size
1.3K
Stars per repository
Useful for distinguishing one flagship-heavy publisher from a repeatable portfolio.
Updated: 2026-08-26(7h ago)GitHub API fallback14 repositories
100%
of the visible star count comes from this organization's top three repositories.
1.3K
stars per repository in this same snapshot.
Rust
is the most common language here, with 7 repositories updated in the last 90 days.
Why this rank
This organization stands out because one flagship repo drives 99% of its visible star count.
Flagship share 99%Breakout repo: iii
Organization pages work best when you separate portfolio breadth from flagship concentration. In iii's case, the visible top three repositories account for about 100% 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 Rust (6), Unknown (3), TypeScript (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 | iii-hq/iii Effortlessly compose, extend, and observe every service in real-time for the first time ever. | Rust | 18.6K |
| 2 | iii-hq/workers | Rust | 99 |
| 3 | iii-hq/spec-forge | Rust | 24 |
| 4 | iii-hq/oh-my-harness You own this harness as a stack of installable workers, and “build your own” stops meaning “fork a framework.” It means “swap a few workers.” | 6 | |
| 5 | iii-hq/skills-and-validation | Rust | 5 |
| 6 | iii-hq/iii-examples Official examples for iii engine | 5 | |
| 7 | iii-hq/console A developer and operations console for the iii engine. | TypeScript | 4 |
| 8 | iii-hq/examples iii examples | TypeScript | 3 |
| 9 | iii-hq/templates | TypeScript | 2 |
| 10 | iii-hq/todo-app | Python | 2 |
| 11 | iii-hq/iii-cli | Rust | 1 |
| 12 | iii-hq/harness-e2e Longitudinal capability and complexity E2E system for Harness | Rust | 0 |
| 13 | iii-hq/iii-cloud-cli Binary releases for the iii-cloud CLI. Source is private. Install via iii cloud or download from releases. | 0 | |
| 14 | iii-hq/homebrew-tap | Ruby | 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.