Skip to the page

What you can ask for / No. 10

Find repositories in your own words

Code on GitHub, GitLab, and Codeberg, with activity, stars, license, and open issues.

Stars measure attention, not upkeep. Ask for both: the stars, a recent push, a license you can use, the language, nothing archived. SpecStream reads GitHub, GitLab, and Codeberg and keeps the date of every observation.

Requests to start from

Three ways to ask. Each one opens in the workspace, read into parts you can check and change.

  1. A1

    Rust command-line tools on GitHub with more than 1,000 stars, pushed to in the last month, under an MIT or Apache license.

    Open it in the workspace
  2. A2

    Python repositories for PDF table extraction with a push in the last 90 days and more than 500 stars.

    Open it in the workspace
  3. A3

    Archived JavaScript charting libraries with more than 5,000 stars. Include the last push date.

    Open it in the workspace

How it reads

Take A1. Before the quote, SpecStream turns it into parts you can check and change. Edit one and the request saves as a new saved version. Anything it can’t support stays visible instead of being quietly dropped.

A1Rust command-line tools on GitHub with more than 1,000 stars, pushed to in the last month, under an MIT or Apache license.

Command-line tools

  • Written inRust
  • FromGitHub
  • Only ifMore than 1,000 stars
  • Only ifPushed to in the last month
  • Only ifMIT or Apache license

Up to 25 results, each one fitting all 4 things you asked forReady.

Details you can ask for

  • Stars
  • Forks
  • Language
  • License
  • Topics
  • Last push
  • Open issues
  • Archived
  • README
  • Releases
  • Homepage

Use them as conditions, ask for them back, or both; the field picker in the workspace shows which work where. Mark a detail required and a result needs evidence for it before it counts. Optional details can come back empty without sinking the record.

Where it looks

Sampled fromSpecStream · No. 10

Sources
GitHub · GitLab · Codeberg

SpecStream picks the sources that fit each request and reads them live. Every fact keeps its source and the time it was read. Where SpecStream looks · How evidence works

From your agent or your code

Ask for the same list from your agent or your code. Your agent sees the price before it runs, then gets every match with the details you asked for. It works within your spending limit. Connect your agent with MCP.

Use SpecStream to find this:
Rust command-line tools on GitHub with more than 1,000 stars, pushed to
in the last month, under an MIT or Apache license.
Show me how you read it and the price before you run anything.

What it costs

You pay for the results that match, at the rate the quote shows.

  • Standard, $0.10 a match: up to 5 facts to check or return, with no related list.
  • Expanded, $0.30 a match: up to 15 facts, plus one related list, such as a company’s jobs or a creator’s posts. 10 related records a result are included, then 10¢ for each further 10.
  • Deep, $1 a match: anything beyond Expanded.
  • A person’s email, +$0.10; a phone, +$0.25 on top of the rate, when the request asks for one. A likely email counts and says likely. Rows without it pay their rate alone.
  • Your own list, $0.05 a row checked. A row that matches pays its rate instead.

New accounts get $10 of work free to start, no card. See pricing

Then what?

Map relationships across a list of repositories by license or language. Or export them to CSV, Excel, JSON, or HTML, share a snapshot with an expiry date, and pick the work up later from wherever you left it.

Keep digging

GrantsPackages

Or flip through the whole crate and ask for any of them the same way.

Go find something