OpenPR
A contribution-intelligence platform that helps developers find open-source issues worth working on through repo-link filtering, timeline scoring, and lightweight bookmark tracking.
OpenPR is a contribution-intelligence platform for developers who want to work on open source without wasting time on issues that are effectively dead on arrival. Instead of surfacing raw issue lists, it filters for issues that still look realistic to pursue and ranks them using contributor-affiliation and timeline signals.
The workflow now supports direct repository inspection. A user can provide a GitHub repo link, OpenPR fetches issues created by contributors, members, and owners, filters out issues that are already assigned or already have pull requests, and then surfaces the remaining opportunities in a more useful priority order.
Inspiration Behind It
The project was driven by repeated experience with open-source issues that looked promising but later turned into wasted effort because the maintainers were inactive, the issue was effectively already claimed, or the pull request stalled without review.
That makes the core value of OpenPR different from a generic search tool. The product is not trying to show more issues. It is trying to reduce contributor regret by helping users judge whether a repository and issue are active enough to justify the time investment, and by warning them when a bookmarked issue later stops being worth taking.
System Architecture
Architecture Diagram
OpenPR
9 nodes
About The Flow / Architecture
OpenPR uses a Next.js and TypeScript frontend, an Express.js backend, PostgreSQL through Supabase, GitHub GraphQL for repository and issue ingestion, Upstash Redis for caching repository-role lookups, and Supabase cron jobs for recurring data collection and cleanup. This stack fits the product because issue ranking depends on repeated background processing, persistent scoring metadata, and controlled API usage rather than only request-time search.
The workflow now has both recurring ingestion and direct repository analysis. The backend can fetch a user-provided repo's issues, keep only issues opened by contributors, members, or owners, exclude issues that are already assigned or already have a pull request, score the remaining set by timeline, and track bookmarked issues in memory so the web app can notify users when a saved opportunity becomes unavailable.
OpenPR helps contributors decide whether an open-source issue is worth their time before they invest effort in understanding a codebase or building a fix. Users can provide a repository link, fetch issues from that repo, and review a filtered set that excludes already assigned work and issues that already have pull requests.
The system combines a Next.js frontend, Express backend, Supabase Postgres, GitHub GraphQL ingestion, Redis caching, cron-driven cleanup, and an in-memory bookmark layer that warns users when a saved issue is no longer available. It stands out because it turns a familiar open-source pain point into a ranking, filtering, and lightweight follow-up workflow with clear product value.