Skip to content

GitHub monitoring for the issues that mention you

Rumoro searches every public repository for your project, SDK or competitors every 15 minutes and sends the issues and pull requests that need you to Slack, a webhook or your AI agent.

$5.80 of free credit · no card · no subscription

Illustrative issues and pull requests
  • Issues + pull requests

    Titles and descriptions across every public repository, not only yours.

  • Every 15 minutes

    Each keyword is searched again, inside GitHub's search limit.

  • Late issues caught

    New issues can take a while to reach GitHub's search. Each check re-reads the last hour.

  • Day one

    A new keyword reads back the newest 10 from the last 30 days straight away.

Notifications, search or monitoring

Why GitHub notifications miss most mentions

GitHub tells you about your own repositories and direct @mentions. Most of what developers write about your project happens somewhere else.

  • GitHub notifications

    Activity in repositories you watch, threads you take part in and @mentions of you or your team. A bug report about your SDK in someone else's repository stays silent.

  • GitHub search

    Finds issues and pull requests across public repositories when you look, with qualifiers like is:issue, is:open or repo:owner/name. It doesn't tell you when something new appears.

  • Rumoro

    Searches every public repository for your keywords every 15 minutes, scores what it finds and sends new matches to Slack, Telegram, email, a webhook or your agent.

How it works

How GitHub monitoring works in Rumoro

Set it up once in the dashboard or with one API call. After that, new issues come to you.

Pulse

+ sdk+ api− heart

Name your project

Your package, SDK or product name, or a competitor’s. Add words that must or mustn’t appear when the name is common.

q="Pulse" created:>=…  sort=created  order=desc
  1. 09:00
  2. 09:15
  3. 09:30
  4. 09:45

Rumoro searches GitHub every 15 minutes

Public issues and pull requests through GitHub’s search API, re-reading the last hour so late issues aren’t missed.

  • orbital/mobile-app · Pulse API pagination?87
  • health-kit · pulse oximeter driver…2
  • acme/web · Pulse SDK retries on 429…79

The issues that matter reach you

Each alert sets its own relevance bar and filters on sentiment and intent, such as questions, comparisons, bug reports, churn or praise, then sends the match to Slack, Telegram, email, a webhook or your agent.

GitHub alerts

Four recipes for GitHub mention alerts

What to follow, the search it becomes and the alert your team gets. Pick one.

Choose a keyword recipe

1Keyword

tidequeue

2Search across public repositories, every 15 minutes

q="tidequeue" created:>=…  sort=created  order=desc

3Alert when

Bug reportQuestion

Track your package or SDK name. Bug reports about it often land in your users' repositories, where you'd never see them otherwise.

# github-mentionsRumoro · APP

🐞 Bug report about tidequeue

GitHub · tidequeue · 🔴 negative · bug report

ttal

tidequeue worker stops processing after a Redis reconnect

acme/billing-service #482

A user hit a reconnect bug in their own service. A maintainer comment with a fix or workaround helps.

Open on GitHubOpen in RumoroInteractedMute ttal

1Keyword

Mentio

2Search across public repositories, every 15 minutes

q="Mentio" created:>=…  sort=created  order=desc

3Alert when

ComparisonComplaint

Teams compare tools in issues and pull requests when they pick a dependency. Follow a competitor's name to see those decisions as they happen.

# github-mentionsRumoro · APP

⚖️ Comparison involving Mentio

GitHub · Mentio · ⚪ neutral · comparison

keelhaul

Evaluate social listening APIs, Mentio vs Rumoro, for the support bot

acme/growth-tools #57

An engineering team choosing between two tools in an open pull request.

Open on GitHubOpen in RumoroInteractedMute keelhaul

1Keyword

Rumoro

Require anyintegrationpluginconnector

2Search across public repositories, every 15 minutes

q="Rumoro" created:>=…  sort=created  order=desc

3Alert when

Relevance ≥ 60

Require words like integration or plugin to catch requests to support your product in other projects, often the first sign of new demand.

# github-mentionsRumoro · APP

🔵 New mention of Rumoro

GitHub · Rumoro · ⚪ neutral

lena-builds

Feature request: a Rumoro connector that triggers on new mentions

flowkit/flowkit #1203

Users of another tool asking for an integration with you.

Open on GitHubOpen in RumoroInteractedMute lena-builds

1Keyword

Pulse

Require anysdkapiclient

Excludeheartoximeter

2Search across public repositories, every 15 minutes

q="Pulse" created:>=…  sort=created  order=desc

3Alert when

Relevance ≥ 70

A name like Pulse turns up in thousands of unrelated repositories. Require a word developers write with it and exclude the ones that never mean you. Excluded items aren't stored or billed.

# github-mentionsRumoro · APP

❓ Question about Pulse

GitHub · Pulse · ⚪ neutral · question

dana-dev

Does the Pulse API client support cursor pagination yet?

orbital/mobile-app #311

A developer asking about a feature of your client library.

Open on GitHubOpen in RumoroInteractedMute dana-dev

Fictional repositories and issues. Required and excluded words are checked on every item Rumoro reads.

Search or monitor

GitHub search, the search API, or monitoring

They read the same public index. They differ in who keeps checking, how GitHub's limits are handled and what reaches you.

QuestionGitHub searchBuilding on the search APIRumoro
Who runs the searchGitHub searchYou, each time you lookBuilding on the search APIYour code, on a schedule you hostRumoroRumoro, every 15 minutes for each keyword
Rate limitGitHub searchNot a concern while you browseBuilding on the search API30 search requests a minute with a token, 10 without, shared by every term you checkRumoroSpaces its searches to stay inside GitHub's limit
Late issuesGitHub searchShows what's indexed when you lookBuilding on the search APINew issues can reach search late, so a strict time check misses someRumoroRe-reads the last hour on every check and skips what it has seen
ResultsGitHub searchPaged as you scrollBuilding on the search APIAt most 1,000 results for one searchRumoroUp to 1,000 new results per check
AuthorsGitHub searchOpen each profile yourselfBuilding on the search APIA login and an avatar. Name, company and bio take more calls per personRumoroProfile, company, location and linked accounts, looked up once
NoiseGitHub searchEvery repository that shares the wordBuilding on the search APIEvery repository that shares the wordRumoroScored 0–100 against your company, bots flagged and muted developers kept out for good
AlertsGitHub searchNoneBuilding on the search APIYours to build and runRumoroSlack, Telegram, email digests and signed webhooks
AgentsGitHub searchCopy and pasteBuilding on the search APIGitHub's MCP server works in repositories you can accessRumoroMCP with scored mentions from every public repository and every other platform

Search limits from GitHub’s REST API documentation.

Beyond alerts

GitHub tracking beyond the alert

See how your project compares, who keeps writing about it, and which keywords are worth their cost.

Your share of voice

See how often your project comes up on GitHub compared with competing libraries, week by week.

The developers behind the mentions

Each GitHub user who mentions you comes with their profile, company, location and linked accounts, plus your tags and notes.

Issues that link to you

Links in matched issues and pull requests are kept, so you can see which ones point to your docs, examples or pricing.

Leave repositories out

Skip your own repositories, where GitHub already notifies you, or any noisy ones, for the whole workspace.

Issues or pull requests

Look at bug reports and questions on their own, or only at pull requests that add or replace your project.

Bots kept apart

Issues opened by bots and automation are flagged, so you can keep them out of alerts with one filter.

Keyword health

See which keywords bring real issues and which mostly bring noise, with suggestions on what to exclude.

Needs attention

An hourly check for sudden spikes, a run of negative issues, noisy keywords or a channel that stopped delivering.

MCP, API, SDKs and CLI

GitHub mentions for your agent, over MCP and API

Rumoro's MCP server gives Claude, Cursor or Codex the public issues and pull requests that mention you, with scores and links. Your agent groups them and drafts replies for you to check.

Bug reports on GitHub with a relevance of at least 60.

curl --get 'https://api.rumoro.dev/v1/mentions' \
  --header "Authorization: Bearer $RUMORO_API_KEY" \
  --data-urlencode 'platform=github' \
  --data-urlencode 'minRelevance=60' \
  --data-urlencode 'intent=bug_report'

200Response · REST, SDKs and CLI

{
  "data": [
    {
      "id": "e7a0…",
      "keyword": { "term": "tidequeue" },
      "post": {
        "platform": "github",
        "url": "https://github.com/acme/billing-service/issues/482",
        "text": "tidequeue worker stops processing after a Redis reconnect"
      },
      "author": { "handle": "ttal", "followers": null },
      "classification": {
        "relevance": 90,
        "sentiment": "negative",
        "intents": ["bug_report"],
        "note": "A user hit a reconnect bug in their own service. A maintainer comment with a fix or workaround helps."
      }
    }
  ],
  "nextCursor": null
}

Coverage, alerts and cost

GitHub monitoring questions

How do I get alerts when my project is mentioned on GitHub?

Add your project, package or SDK name as a keyword. Rumoro searches the titles and descriptions of public issues and pull requests every 15 minutes, scores each match for relevance, sentiment and intent, and sends the ones you care about to Slack, Telegram, email, a webhook or your AI agent. Lower-volume keywords can arrive as a daily digest instead.

Can I monitor GitHub issues in other people's repositories?

Yes. The search covers every public repository, so a bug report about your SDK filed in a customer's repository reaches you with the repository, the author and a link to the issue.

Do I need a GitHub token or API key?

No. Rumoro searches GitHub with its own access. You don't connect a GitHub account or create a token, and nothing is posted in your name.

Why don't GitHub notifications show these mentions?

GitHub notifies you about repositories you watch, threads you take part in and @mentions of you or your team. When someone names your project in their own repository without tagging you, nothing reaches you. Rumoro searches for the name itself.

How do I search GitHub issues for mentions of my project?

GitHub search and its advanced search page find them when you look. In GitHub's search syntax, put the name in quotes and add qualifiers such as is:issue, is:open or sort:created-desc to see the newest first. Rumoro runs that search for you every 15 minutes and only sends what's new and relevant.

Does Rumoro read GitHub comments or code?

No. Rumoro matches the titles and descriptions of public issues and pull requests. Comments under them and code in repositories aren't covered, so a mention that only appears in a reply won't arrive.

How fast do GitHub mentions arrive?

Each keyword is searched every 15 minutes. A new issue can take a while to show up in GitHub's search, so each check re-reads the last hour and late issues still arrive, once. A new keyword also reads back the newest 10 from the last 30 days.

Is there a GitHub Slack integration for mentions?

Yes. GitHub's own Slack app posts activity from repositories you subscribe to. Rumoro posts something different, the issues and pull requests anywhere on GitHub that mention your project, with the repository, the AI relevance score, a note on why it matters and buttons to open it, mark it handled or mute the author.

What is the GitHub API rate limit for search?

The GitHub search API allows 30 requests a minute with a token and 10 without, and returns at most 1,000 results for one search. If you build your own polling, every term you watch shares that budget. Rumoro spaces its searches to stay inside it.

Is Rumoro a GitHub MCP server?

Not in the sense of GitHub's own MCP server, which lets an AI tool work in repositories you have access to. Rumoro's MCP server gives Claude, Cursor or Codex the public issues and pull requests that mention you, scored and linked, next to every other platform.

Can I leave my own repositories out?

Yes. Add them to the excluded repositories in your workspace settings and their issues and pull requests are dropped before they're stored or billed. Most teams leave out repositories where GitHub already notifies them.

What about issues opened by bots?

Each mention is checked for whether it reads as machine-made, such as a bot account or a scheduled post, and flagged. Filter the feed or an alert to people only and bot activity stays out of the way.

Does Rumoro cover private repositories?

No. Only public repositories are searched.

Is there a free GitHub monitoring tool?

Every Rumoro account starts with $5.80 of credit and no card, enough for your first keyword for a month and 100 mentions on top. After that it's $5 a keyword a month and $0.008 per match, with no subscription.

How much does GitHub monitoring cost?

$5 per keyword a month, charged by the day, plus $0.008 per matched issue or pull request. There's no subscription. You top up a balance, and a new account starts with $5.80 of credit and no card.

Learn more

More on GitHub monitoring, MCP and the API

One keyword, every platform

GitHub is one of 16 sources

Add a keyword once and it listens everywhere you choose, scored the same way and sent to the same alerts, API and agent.

Reply to the issue while it’s still open

Your first keyword is on us. $5.80 of credit, no card.