Star it. Understand it. Find it again.

Turn GitHub stars into an actual developer workspace.

StarDash syncs your starred repositories, adds tags, collections, notes, AI repo analysis, contribution triage, and intent-first discovery so saved projects become useful again.

5,000
repos per sync pass
6
workflow statuses
24h
client cache window
StarDash dashboard preview
Search notes, tags, status, language, and owner
Read README and repo intel without tab sprawl
Find contribution issues before context goes cold
The pain

Starring a repo is easy. Recovering the reason later is the hard part.

StarDash is built for developers who use stars as research, backlog, evaluation queue, and long-term reference, then need more than GitHub's native starred page.

01

Stars are a weak memory system

GitHub remembers that you clicked a star. It does not remember why, where it fits, whether you tried it, or what you wanted to compare it against.

02

Search breaks when intent is fuzzy

The repo name is rarely the thing you remember. You remember the use case: async runtime, auth library, promising CLI, abandoned dependency.

03

Evaluation context gets scattered

READMEs, issue health, notes, contribution candidates, and trend signals live in separate tabs. StarDash pulls them into one operating surface.

Product tour

A homepage that shows the app, not a vague promise.

The public page now mirrors the real product: curation dashboard, Discover search, repo intelligence, and contribution triage.

Dashboard
Curated star library
AI & ML42
Frontend81
CLI Tools33
Databases18
notes: background jobs tag:rust status:want-to-try
vercel/next.js
TypeScript · 128k stars · README cached
Currently Using
astral-sh/uv
Rust · 62k stars · README cached
Want to Try
charmbracelet/bubbletea
Go · 31k stars · README cached
Reference
Discover
Intent-first repository search
prod-ready CLI frameworks
parse intent
search GitHub
rank evidence
oclif/core

Command framework for Node.js CLIs

TypeScriptsaved search
urfave/cli

Simple, fast package for Go CLIs

Gosaved search
Repo Intel
Maintenance and adoption read
84
Healthy
production ready
MaintenanceActively maintained
CommunityMixed sentiment
Release cadenceRecent release found
Recommendation: good candidate for production usage after checking open migration issues.
Contribute
Ranked issue opportunities
Add test coverage for config parser
beginnertestsAI brief
86
Improve docs for custom providers
beginnerdocsAI brief
78
Refactor release workflow retry logic
intermediateinfraAI brief
64
Contribute workspace

Turn favorite repos into open-source work you can actually start.

The Contribute page scans active starred repos with open issues, ranks opportunities by fit and quality, then gives you filters and an AI brief so you can decide what is worth opening.

Filter the work

Language, difficulty, contribution type, and text search over repo or issue title.

Ranked issue feed

Scores blend labels, body context, recency, comments, pinned repos, risks, and repo activity.

AI contribution brief

Summary, why it fits, first steps, likely files, questions to ask, and a prompt.

Assistant-ready handoff

Copy the generated coding assistant prompt and paste it into Codex, Claude Code, or another tool.

AI brief schema
summarywhyItFitsfirstStepslikelyFilesquestionsToAskcodingAssistantPrompt
Contribute
Open issue workspace
language
TypeScript
difficulty
Beginner
type
Docs
search
cache
24Matches
11Beginner
40Repos scanned
vercel/next.jsbeginnerdocs
Improve docs for route cache invalidation
Maintainers classified the issue
88%
charmbracelet/bubbleteabeginnertests
Add regression test for resize event handling
Small scoped contribution
81%
tursodatabase/libsqlintermediateinfra
Clarify Docker workflow failure mode
Recently active discussion
73%
Contribution brief
Ready-to-copy issue plan
Summary

Clarify when route cache invalidation runs and add a short example for nested layouts.

First steps
  1. Read the issue and linked discussion.
  2. Find docs covering cache invalidation.
  3. Add the smallest example that answers the report.
codingAssistantPrompt
copy
You are helping resolve GitHub issue #4821 in vercel/next.js.

Goal: improve docs for route cache invalidation.
Start by inspecting the docs routing cache section, then propose the smallest docs patch with a runnable example.
Feature set

Everything is centered on one job: make saved repos usable.

StarDash covers the full loop from sync and organization to evaluation, rediscovery, and contribution planning.

Grid/list views

Curation dashboard

Sync up to 5,000 starred repositories, then filter by language, status, tag, collection, archived state, or uncategorized state.

Notes included

Search your own memory

Search repo names, owners, descriptions, private notes, and tags without rebuilding context from GitHub every time.

You stay in control

AI taxonomy pass

Generate 5-12 collections and a shared tag vocabulary from your starred repos, then review and edit the result.

Cached per repo

Repo Intel

Run AI-assisted repo analysis with health score, maintenance verdict, adoption readiness, pain points, and practical recommendations.

Issue triage

Contribution finder

Scan open issues across starred repos, rank them by fit and quality, then generate a concise brief before you start.

Intent-first search

Discover search

Describe what you are building and StarDash runs an AI-guided GitHub repository search with saved searches and personalized themes.

Seeded from recent stars

Trending signals

Analyze your most recent starred repos to surface popular, active, and hidden-gem repositories already related to your interests.

Local history

Recently viewed

Jump back into repos you opened from dashboard, trending, or detail views without retracing your filters.

Personal taxonomy

Tags, collections, statuses, notes, and pins explain why a repo matters.

The dashboard stores user-owned metadata separately from the global repo catalog, so your labels, notes, and workflow state remain personal.

Want to TryCurrently UsingTried - LikedTried - DroppedJust InterestingReference

Tag vocabulary

Create, edit, color, and delete tags from Settings or while assigning repos.

Collections

Group related repositories and track repo counts across your personal taxonomy.

Private notes

Attach freeform notes and save them directly from the repo detail drawer.

Pinned repos

Keep the repos you actually use above the long tail.

Workflow

A practical loop for repo research.

No CSV import flow and no separate knowledge base to maintain. The app starts from your GitHub stars and keeps the workflow close to the repos.

01

Connect GitHub

Supabase OAuth stores the provider token server-side so StarDash can sync your starred repositories and refresh metadata.

02

Make the backlog navigable

Use search, sorting, pinned repos, status labels, tags, and collections to turn passive stars into an active reference library.

03

Add judgment

Attach notes, read READMEs inline, inspect repo health, and generate contribution briefs when a repo deserves a closer look.

04

Keep resurfacing value

Use recently viewed history, Discover searches, and trend buckets to find the right tool when the original star is long forgotten.

AI where it helps

The AI features do first-pass organization and evaluation, then get out of your way.

StarDash uses model calls for taxonomy generation, personalized Discover themes, repo intel, and contribution briefs. The outputs are editable, cached where useful, and tied back to concrete repo data.

Taxonomy
Collections and 15-25 tags from repo summaries.
Discover
Adjacent search themes from your starred repo sample.
Intel
Health scores, sentiment, readiness, and recommendations.
Briefs
Issue summaries, first steps, likely files, and assistant prompts.
AI operations panel
Representative system events
telemetry enabled
categorize-taxonomy
500 repo summaries
complete
personalized-theme-search
100 repo sample
cached
contribution-brief
issue metadata
ready
repo-intel
health metrics
shared cache
Supabase Auth

Session checks on every request

Supabase middleware refreshes the session and protected routes validate users with `supabase.auth.getUser()` before loading app data.

8h cookie

GitHub tokens stay server-side

OAuth access uses an `httpOnly`, `sameSite=lax` cookie. If that cookie expires or is missing, route handlers repair it from a server-only token table.

RLS

Your metadata is scoped to you

Tags, collections, notes, statuses, saved Discover searches, and repo assignments use RLS policies keyed to `auth.uid()`.

Local key

Bring your own AI key

Optional AI provider keys are saved in your browser localStorage, sent as request headers only for AI calls, and can be cleared from Settings.

Trust boundaries
What runs where
Browser
Theme + view cache
Optional AI key
Recently viewed history
Server routes
GitHub token lookup
AI provider selection
Sentry error capture
Supabase
Auth sessions
RLS user metadata
Service-role admin jobs
Guardrails

System-key AI calls are rate-limited, cron and observability test routes require `CRON_SECRET`, and cached Discover searches are capped per user.

Observability

Sentry records runtime errors and Langfuse receives AI SDK telemetry only when configured, with traces flushed from long-running AI routes.

Security & privacy

Built around private developer context, not public leaderboards.

StarDash stores personal repo context behind your authenticated account, keeps GitHub access out of client code, and makes AI usage explicit.

Plain-language privacy boundary

Repo metadata, notes, tags, and search/AI outputs are used to power your workspace. AI features send the relevant prompt context to the configured model provider; using your own key routes those calls through the provider you choose.

Stop treating GitHub stars like a junk drawer.

Connect GitHub once. Sync the backlog, organize it, inspect the repos that matter, and return to the right project when you need it.

Your stars, notes, tags, and collections stay tied to your account.