Skip to content
All voluntary projects

Open Source Radar

Open source issues you can actually start today.

Most good first issue lists go stale within days: the issue is already claimed, already has a pull request, or sits in a project that stopped merging outside contributions. Open Source Radar checks every issue against the GitHub API twice a day and only lists the ones nobody is working on, from projects with recent commits. Each project is also scanned for the rules that decide whether a pull request can be merged at all: contributor license agreements, DCO sign-off and AI contribution policies.

Role
Solo. I built the pipeline, the website and the guide.
Period
2026, ongoing
Status
Live, refreshed twice a day
Built with
Python · GitHub GraphQL API · GitHub Actions · GitHub Pages · Vanilla JS
3,500+
open, unclaimed issuesNewcomer and help wanted labels
1,200+
active projectsCommits in the last 60 days
30
languages, 12 topicsPlus a searchable website
2x
refreshed every dayScheduled GitHub Actions workflow

The problem

What was actually wrong

Finding a first issue is harder than it looks. Labels like good first issue attract so much attention that the easy ones are claimed within hours, and a static list cannot tell you that.

The rules that decide whether your work can be merged are scattered: a CLA in one project, DCO sign-off in another, a ban on AI generated code in a third, and workflows that auto close pull requests from accounts they do not recognise. Contributors usually find out after doing the work.

Approach

What I built

Discover. The GitHub search API finds public, non archived repositories in 30 languages with at least 500 stars, recent commits and open newcomer issues.

Filter. A batched GraphQL query pulls each project's newcomer labeled issues with their assignees and linked pull requests. Anything assigned, locked, linked to an open or merged pull request, or untouched for six months is dropped.

Explain. Contribution files are scanned for AI policies, CLA and DCO requirements, and the results ship as badges next to every issue, with a link to the source file because automatic detection can be wrong.

Publish. A scheduled workflow renders Markdown pages by language and topic, a projects directory and the JSON behind a static website, then deploys it. A safety check refuses to publish a run that lost most of its issues, so an API outage cannot wipe the lists.

Built for everyone

Free and open source. Use it, share it, or help improve it.