Public GitHub repositories
Know what to do with a repo
RepoScout reads a public GitHub repository against the interests, skills and criteria you wrote, and tells you which of twelve actions are worth taking: star, watch, fork, use, contribute, or skip.
Where it works. Any public repository page on github.com, including its issues, pull requests and file tabs. It judges when a repository opens, or when you click Re-check. It does nothing on profiles, organisations, search, marketplace or private repositories. Not affiliated with or endorsed by GitHub, Inc.
One payment for the paid features, no subscription.
A small widget library. npm install widget. Pushed 3 days ago, 7 of the last 10 pull requests merged.
Boilerplate for a Next.js SaaS. Clone it, rename it, ship. Marked as a template on GitHub.
DEPRECATED: use acme/new-cli instead. Archived by the owner. Last push 3 years ago.
Every other action stays quiet. The badge says "Avoid" and nothing else.
Example output. Real results depend on the page.
How it works
Set up once. No account, ever.
Install it
Add RepoScout to Chrome. No account, ever.
Add your key
Paste your TypeSafe API key into the options page. RepoScout checks it with one small request before you rely on it.
Use it where you already are
Star, watch, fork, clone, use as a dependency, use as a template, bookmark, add to your list, sponsor, contribute, avoid, or skip. Tick the ones you care about.
What it does
Know what to do with a repo
Twelve actions, each judged on its own
Star, watch, fork, clone, use as a dependency, use as a template, bookmark, add to your list, sponsor, contribute, avoid, or skip. Tick the ones you care about.
Judged against you, not in the abstract
You write your interests, your technologies and what you build once. A Rust crate reads differently to a Rust developer than to a designer.
Your own conditions for contributing
Hard filters checked in code for free, plus conditions in your own words, such as "allows AI-assisted contributions", tested against the CONTRIBUTING file.
Bring your own TypeSafe key
It runs on Jev, TypeSafe's judgment model, using a TypeSafe API key you create yourself.
You use your own TypeSafe API key, and the request goes straight from your browser to TypeSafe. There is no server in between, because a key shipped inside an extension is a key anyone can read out of the zip.
TypeSafe publishes the price of Jev as $0.042 per million input tokens, with no charge for output. What a page costs depends on how long it is. radrebeldeveloper receives nothing: not the page text, not an identifier, not a count of how often you use it.
Pricing
One price. Pay once. Use forever.
Free
The judgment on every public repository, all twelve actions, your profile and your criteria, with no limit.
$4.99 once
The curated list of everything you saved, revisit reminders, and export to CSV, Obsidian or Notion.
No subscription. Judgments are never metered: you are paying for your own inference already, so capping them would be charging you twice.
One payment for the paid features, no subscription.
Questions
The ones worth answering.
Why do I need my own API key?
Because a key shipped inside an extension is a key anyone can read out of the zip. Yours stays yours, and so does the spend. It runs on Jev, TypeSafe's judgment model, using a TypeSafe API key you create yourself.
What does it actually cost to run?
TypeSafe publishes the price of Jev as $0.042 per million input tokens, with no charge for output. What a page costs depends on how long it is.
Which browsers?
Chrome. It is published on the Chrome Web Store.
What if it is not what I wanted?
Email contact@radrebeldeveloper.com within 14 days and you get your money back. No explanation needed.