GitHub Opportunity Radar
Pricing
Pay per usage
GitHub Opportunity Radar
Find and rank public GitHub issues that are practical contribution opportunities using keywords, language, stars, and activity filters.
Pricing
Pay per usage
Rating
0.0
(0)
Developer
Steven Feng
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
a day ago
Last modified
Categories
Share
GitHub Opportunity Radar searches public GitHub issues and ranks practical contribution opportunities for independent developers. It is intended for discovery and prioritization, not for acting on GitHub content.
What It Does
- Searches public GitHub issues from user-provided keywords.
- Applies lightweight filters such as language, repository stars, and excluded repositories.
- Scores opportunities based on issue and repository signals.
- Returns ranked records that can be reviewed before a contributor chooses what to work on.
Input Fields
keywords: issue search terms.languages: optional repository languages.minStars: minimum repository stars.maxResults: maximum records.excludeRepos: public repositories to skip, usingowner/repofull names.includeClosedRecently: when true, includes recently updated closed issues in search results.githubToken: optional secret for higher API limits.
Output Fields
Each dataset item includes:
status:ok,partial, orfailed.errors: non-fatal limitations or per-record errors.evidence: source URLs used for the record.observedAt: ISO timestamp for the run.keyword: matched input keyword.searchQuery: GitHub search query used to find the issue.repository:fullName,url,stars,language, andpushedAt.issue:id,number,title,url,state,labels,createdAt,updatedAt,comments, andassignees.opportunityScore: numeric opportunity ranking.riskFlags: risk labels that explain possible drawbacks.suggestedAction: manual follow-up recommendation.
Limits And Safety Boundaries
This Actor uses public GitHub search/API data only. It does not claim issues, comment on GitHub, open pull requests, inspect private repositories, or make changes to repositories.
Linked pull request timeline analysis is not included in the MVP.
Excluded repositories are applied after lightweight candidate collection because GitHub issue search returns repository API URLs, not guaranteed owner/repo names.