Awesome Solana OSS: how to use the open-source map

StockpileLabs/awesome-solana-oss is a curated “awesome” index of open-source Solana repositories on GitHub. Maintainer: Joey Meere (@joeymeere). Purpose stated upstream: discover code to learn from, find projects to contribute to, and get a rough gauge of the Solana OSS surface.

This is a map, not a package manager. Rows go stale; “actively maintained” is a claim until you check the target repo. Use the list for breadth, then run a short verification loop before you depend on anything.

Click to zoom

People and links

Contribution bar (upstream)

• Submit via PR with a suggested add
• Repository must have a valid open-source license (MIT, GPL, Apache 2.0, etc.)
• Tables typically carry: name, description, team/dev, actively maintained?, link

If you maintain a licensed Solana repo missing from the shelf, open a PR that matches the nearest section’s table format — don’t invent a new column set.

Section map

Current README sections (names can shift as the list is edited):

Expect duplicates across sections (e.g. Anchor in starters and tooling). That is normal for awesome lists; pick the section that matches your job, not every mention.

How to use it as a builder (workflow)

1. Pick a section from the job (tooling vs DeFi vs validator …)
2. Shortlist 2–5 repos from description + team
3. For each candidate:
   - License file present and acceptable to your counsel
   - Default branch recent commits / open PRs / CI green
   - README install path works on your machine
   - Stars/forks as weak signal only
4. Prefer primary upstream over abandoned forks listed by accident
5. Pin a commit/tag in YOUR repo — never “main of a random awesome row”

# Open the list
open https://github.com/StockpileLabs/awesome-solana-oss

# Quick health on a candidate (example)
gh repo view coral-xyz/anchor --json stargazerCount,pushedAt,licenseInfo,url
gh api repos/coral-xyz/anchor/commits?per_page=1 --jq '.[0].commit.author.date'

Reading the “actively maintained?” column

• Yes means the list author believed it was active when the row was written — re-check pushed_at and default-branch CI.
• No can still be useful as a reference implementation (read code, don’t ship deps).
• Missing CI + years since last commit → treat as archive even if the cell says Yes.

How this list relates to other awesome shelves

DevRels also covers security-focused awesome lists in Awesome Solana lists: security map. Split responsibilities:

Adding your repo (checklist)

1. SPDX-compatible license in the root.
2. Public GitHub repo with a clear README and build instructions.
3. Choose the single best section; mirror existing table markdown exactly.
4. Honest maintenance flag — don’t mark Yes on a frozen weekend experiment.
5. PR description: one sentence what it does + why it belongs in that section.

Summary

awesome-solana-oss is Joey Meere’s licensed-repo catalog for the Solana open-source landscape. Navigate by section, treat maintenance flags as hints, and always verify license + recent activity on the target repository before you teach from it, contribute to it, or vendor it. Pair it with security-focused awesome lists when the question is “how do I not get wrecked,” not “what exists.”