Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problemsGitHub can show an issue as open and unassigned even when someone has already claimed it, a pull request is underway, or maintainers have marked it as not ready. Ankith M says that when he checked 31 such results in kestra-io/kestra, none were actually free. He built Unclaimed to help his best friend find work that appeared available—and to show the evidence behind that assessment.
Why can an open GitHub issue already be taken?
“Open” describes an issue’s state, not whether a new contributor can start work without duplicating someone else. An issue can stay open while a pull request is linked to it, a contributor says they are working on it, or a maintainer says it is not ready for contributions. An assignment is another useful signal, but its absence does not prove that nobody has claimed the work.
As an Amazon Associate I earn from qualifying purchases.
That distinction matters especially to beginners looking for a good first issue. Finding one that is approachable is only part of the task; a contributor also needs to know whether it is available and whether maintainers are ready to receive a change.
Free tools Windows power users keep installed
One-click scans. No signup required.
What did Ankith M find in the Kestra search?
In his October 4, 2026 DEV Community account, Ankith M says GitHub search returned 31 open, unassigned good-first-issue results in kestra-io/kestra. His review found that 21 already had a pull request, 8 had people asking to work on them, and 2 were marked “not ready for contributions.” He concluded that 0 were actually free. He also reports that one issue had three pull requests and another had as many as 11 people asking to work on it.
#1 Best Overall
Those numbers describe the author’s review of that particular set of results, not a current count for Kestra or a general measure of GitHub issues. The account does not include an issue-by-issue appendix or a reproducible query, and the statuses may change over time.
How does Unclaimed assess issue availability?
Unclaimed is described as combining direct GitHub signals with model-assisted reading of issue comments. The aim is not just to label an issue available or taken, but to make the reasoning inspectable.
First, it checks concrete GitHub signals
The tool checks whether an issue has assignees, whether pull requests are linked—including open or merged pull requests found in the issue timeline—and whether the project displays a “not ready for contributions” banner. These signals can rule out an issue even when GitHub’s search results still show it as open and unassigned.
Then it reads comments when the signals are inconclusive
For cases that need interpretation, the account says Unclaimed uses Gemma 3 4B through Ollama to read the issue and recent comments. It extracts structured details such as who asked for assignment, who says they are working on the issue, maintainer decisions, a short task summary, and an estimated difficulty. The result is described as including the relevant comment, the commenter’s avatar, the date, and a link to the evidence.
That evidence is important: “claimed” can be expressed in ordinary language rather than recorded as an assignment, and comments can be ambiguous. A status estimate is more useful when a contributor can inspect the actual discussion instead of having to trust a bare label.
Repository conventions still matter
Unclaimed is described as accepting either a public repository or a link to one issue. Labels for beginner-friendly work are not standardized across projects, so the tool’s ability to recognize a repository’s convention matters. Ankith M reports that it recognized Zed’s .contrib/good first issue label and found 4 of the 15 newest issues free. That is his demonstration, not an independently verified result or a guarantee for other repositories.
What did building it reveal about the hard parts?
Ankith M describes the implementation as plain Node.js, a single HTML page, Gemma 3 through Ollama, and two Railway containers. He says the 1B model missed claimants in one example, while moving to 4B improved the results. On CPU, he reports processing times of about 6 to 16 seconds per issue; that is his reported experience, not a benchmark for other hardware or deployments.
He also says a small code rule that corrected the model’s output worked better than asking the model alone to identify only genuine self-claims. The distinction matters because a comment can mention taking an issue without clearly establishing that the commenter is the person who will work on it.
- Long responses: Requests timed out while the model generated lengthy JSON.
- Private organization membership: Maintainer comments were sometimes misread when organization membership was private.
- Pull-request visibility: A read-only GitHub token sometimes made open pull requests appear absent. The author says he addressed this by also searching for pull requests that mention the issue.
These reported problems show why a single field or label may not settle availability. They also mean that a tool’s conclusion should be checked against the linked GitHub discussion, particularly when the status is uncertain.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.How much confidence should contributors place in the results?
Ankith M says: “I checked it against 8 real issues I had read by hand, and it got all 8 right.” That is a small, self-reported manual check. It does not establish independent accuracy, performance across repositories, or how well the tool handles issues with unusual workflows. The account also notes that model size and API visibility affected results.
For a contributor deciding whether to begin work, use an availability result as a shortcut to the evidence—not as permission from the maintainers. Open the issue and review the linked pull requests, recent comments, assignment, and any readiness notice. If a person has asked to work on it or the maintainer’s position is unclear, ask in the issue before investing in a change.
Recommended Free Tools
What is the practical lesson for finding a good first issue?
Search labels and open status are a starting point, not a complete availability check. Look for evidence of assignment, an existing pull request, a claim in the comments, and maintainer readiness. Unclaimed is Ankith M’s attempt to bring those clues together and display their sources; the underlying decision still depends on the repository’s current discussion and conventions.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
