Stackmatch
Finding developers who build with the same tools you do
Overview
Stackmatch helps developers find people and organizations that build with similar technology stacks. It scans public GitHub package.json files, builds dependency fingerprints, and surfaces stackmates, package communities, language pages, topic communities, and public developer profiles.
The Problem
Developer discovery is usually based on bios, not shipped code
Finding relevant builders is hard when search depends on self-written profile text, social graphs, or broad labels. The tools people actually use in public projects are a stronger signal, but that signal is buried inside repositories.
- GitHub profiles do not make stack overlap easy to scan
- Package communities are fragmented across repositories and organizations
- Developer discovery often favors popularity over practical relevance
- Recruiting and collaboration workflows need better technical context
- Private stack analysis needs clear boundaries around what is and is not stored
The Solution
Dependency fingerprints as a discovery layer
Stackmates
The product surfaces developers whose real project dependencies overlap with a selected user, organization, package, or community.
Public Profiles
Indexed developers and organizations get public pages that summarize their visible stack signals.
Package and Language Pages
Package leaderboards, language pages, and topic communities make it easier to browse technical ecosystems.
GitHub Sign-in
Developers can sign in with GitHub to claim their profile and connect the product to their real identity.
Private Stack Sync
A separate GitHub App consent flow can analyze private stacks while storing aggregate dependency names, counts, and sync status instead of source code or private repository details.
Search and Owner Scanning
Search flows and queued profile scans help keep discovery data fresh as developers and organizations are explored.
Technical Implementation
A TypeScript monorepo built around live product data
Technology Stack
- Next.js
- React
- Tailwind CSS
- Convex
- Better Auth
- GitHub OAuth
- Radix UI
- Lucide
- @stackmatch/ui
- OpenPanel
- pnpm
- Turborepo
- Biome
- Vitest
- Testing Library
- jsdom
Dependency Indexing Model
Public package.json data is converted into dependency fingerprints that can power profile, package, language, and community discovery surfaces.
Privacy-aware Private Sync
Private repository analysis is opt-in through a separate GitHub App flow and is designed around aggregate dependency metadata instead of storing source code, private paths, repository names, commit messages, or SHAs.
Convex Product Backend
Queries, mutations, actions, and scheduled jobs support live discovery, profile scanning, and product workflows.
Shared Product System
The monorepo includes shared packages for API/config/constants/localization/UI/utilities, keeping the web app and product logic aligned.
Results
The product is live with docs and a verified privacy model. Usage metrics are left as placeholders until the correct product analytics project is confirmed.
Verified Signals
- Live product available at stackmatch.dev
- Public documentation available at stackmatch.dev/docs
- OpenPanel integration exists in the web app, but product metrics require verified project identity
Impact
A more practical way to discover builders and technical communities
- Uses real project dependencies as a discovery signal instead of relying only on profile text
- Connects developers, organizations, packages, languages, and topics through shared stack overlap
- Gives claimed profiles and private sync a clear consent and privacy boundary
- Creates a foundation for ecosystem pages, recruiting workflows, and community discovery
What I Learned
- 01Developer discovery needs explainable matching signals, not just rankings
- 02Public GitHub metadata can be useful when the product clearly communicates its limits
- 03Private repository workflows need separate consent, narrow storage, and direct language
- 04Search experiences need fast exit paths and queued refreshes when data is stale
Explore Stackmatch
Find developers who build with your stack