What is OSSPath
A map of the Rust ecosystem. Not a comprehensive index — a curated one. Jobs, repositories, funding programs, organizations, and community signals, selected and maintained by hand.
The goal is to give someone working in or around Rust a clear picture of what exists and who is involved — without noise.
- Jobs →Remote Rust engineering roles. Each listing is reviewed before it appears. No aggregation, no scraping.
- Repos →2,100+ open-source Rust repositories indexed by stars, activity, license, dependencies, and ecosystem.
- Funding →Grants, fellowships, and sponsorships for Rust ecosystem work — from the Rust Foundation, NLnet, and others.
- Organizations →Companies and teams with significant public Rust output. Profile pages show repos, ecosystems, and open roles.
- Ecosystems →The corpus grouped by domain: web, embedded, async, WASM, game development, databases, and more.
- Community →Newsletters, forums, podcasts, and working-group channels worth following.
- —Not a job board aggregator. There is no automated scraping. Jobs are listed one at a time.
- —Not a startup directory. Organization pages exist only when the org has meaningful public Rust output.
- —Not a comprehensive repository search engine. The corpus is curated, not exhaustive.
- —Not affiliated with the Rust project, the Rust Foundation, or any company listed here.
Everything here was added by hand. The goal is not completeness — it is usefulness.
For repositories: included based on stars, commit recency, license, and dependency graph signal. A repository inactive for years with few dependents is not useful to include. A crate with modest star counts but broad dependency coverage across the corpus is.
For jobs: listed only when the posting is currently active, the role genuinely uses Rust, and the company is one worth finding.
For funding: listed when the program is accepting applications or recurring annually.
Full inclusion criteria, review cadence, and classification rules are documented on the methodology page.
The corpus is maintained manually. Stale data is inevitable — postings expire, repositories get archived, organizations change direction.
If something is wrong, send a correction via the contact page or open an issue on GitHub. Pull requests are welcome for data corrections and new additions that fit the inclusion criteria.
CONTRIBUTING.md →A solo project by Adarsh. Built because there was no single place to see the Rust ecosystem as a connected graph — repos, funding, organizations, and jobs as related nodes rather than separate lists.