Why is the count so high for some names?

GitHub search matches pull request and issue bodies, so a widely used package turns up in every change that touches it. Bots are already excluded; the issue and pull request split shows what is left.

Does it search GitHub Discussions?

No. GitHub’s REST search does not include Discussions, so neither this tool nor FishOut counts them. Octolens says it monitors discussions and READMEs; that is a real difference.

Why don’t you show the repository or the author?

Many repositories are named after a person. The title and a link are enough to decide whether to open it, and the link shows the rest on GitHub.

Does it see private repositories?

No. Only public issues and pull requests are searchable, here and in the product.

Can I get GitHub mentions in Slack?

Yes. GitHub is on every FishOut plan, including Free, and every alert channel is too. An agent can send only the ones labelled “Has a problem”.

Find GitHub issues and pull requests that name your product

Bug reports, integration requests and migrations often name a tool on GitHub before anyone tweets about it. See a week of issues and pull requests that mention yours, split by type and state.

Live checks are not switched on yet. The result below is a real one, captured on the date shown.

“Turborepo” · last 7 daysSample · 20 Oct 2026

~1,266

mentions in the last 7 days

Counts only — relevance not judged here

GitHubanswered1,266

whole-word, of 1,889 raw matches · 10 issues · 57 PRs · 20 open, 47 closed, of those read

Threads to readnewest first

docs(external-api): AP / GL export spec — numeric fields are numbersPull requestnow

deps: bump turbo to 2.11.9Pull requestnow

feat(accounting): mapping-only export UI + Accounting settings page for gl_settingPull requestnow

chore(web): Next.js 앱 생성과 design-system-a 적용Pull requestnow

Scaffold Solar Portfolio Memory (M0)Pull requestnow

These are whole-word matches before AI triage. FishOut counts only the posts it judges relevant toward a plan — Free covers 500 a month — and filtered noise never counts.

Watch your own keywords free

[01] HOW THE COUNT IS MADE/ METHOD

Issue search, quoted

GitHub’s search API is asked for the exact phrase in issues and pull requests created in the last seven days. It searches titles and bodies across public repositories.

Bots left out

Dependabot, Renovate and GitHub Actions open thousands of pull requests a day that name packages in their body. They are excluded, because a version bump is not anyone talking about you.

Whole words, then scaled

Of the hundred newest results, those that contain the name as a whole word give a share, and GitHub’s total is scaled by it. A package whose name is also a common word drops sharply here.

What it does not search

Discussions are not in GitHub’s REST search, so they are not counted, and private repositories are never seen. Titles are shown; authors and repository owners are not.

[02] WHAT TO DO WITH THE NUMBER/ TRIAGE

A GitHub issue that names you is usually a support ticket you did not get

Someone hit a problem integrating your product into theirs and filed it in their own repository. FishOut labels those “Has a problem”, and an agent can send them to the people who can help before the thread goes cold. How relevance works.

acme/acme-cliissue · open40m

Build fails after upgrading to the latest release on Windows

Reply, carefullyHas a problem

example/webpull request6h

Migrate the monorepo build to the new task runner

Comparison

example/docsissue · open1d

Feature request: an official integration guide

Question

[03] STEP BY STEP/ 4 STEPS

Search the package or product name

Use the name people put in their code and README, which is often the package name rather than the brand.

Separate issues from pull requests

Issues are people with a problem or a request. Pull requests are mostly migrations and integrations — a useful adoption signal.

Read the open issues first

An open issue that names you is the one where a comment from your team still changes the outcome.

Route them automatically

In FishOut, an agent can send every GitHub post labelled “Has a problem” to your support channel.

[04] THE SAME CHECK, EVERY HOUR/ IN THE PRODUCT

The same search, routed to support

FishOut checks GitHub hourly on every plan. An agent reads the labels and does the routing, so a bug report in someone else’s repository reaches the right channel instead of a weekly search tab.

GitHub problems to support14 runs this week

When

A post arrives from GitHub

Label is Has a problem

Relevance is 60 or more

Then

Alert #support in Slack

Assign to the on-call engineer

[05] FREE TOOL, OR A MONITOR?/ COMPARED

This search, FishOut Free, or Octolens?

Octolens is the vendor that writes most about GitHub monitoring. It covers some GitHub content this search does not.

Issues: This free toolYesFishOut FreeYesOctolensYes [source]
Discussions and READMEs: This free toolNoFishOut FreeNoOctolensYes [source]
Pull requests: This free toolYesFishOut FreeYesOctolensNot listed [source]
Price to keep watching: This free toolFree, one-offFishOut FreeFree for 10 keywords; Plus $19/moOctolensFrom $159/mo billed annually after a 7-day trial [source]

This free tool, FishOut Free and Octolens, compared
	This free tool	FishOut Free	Octolens
Issues	Yes	Yes	Yes [source]
Discussions and READMEs	No	No	Yes [source]
Pull requests	Yes	Yes	Not listed [source]
Price to keep watching	Free, one-off	Free for 10 keywords; Plus $19/mo	From $159/mo billed annually after a 7-day trial [source]