Any Update? Checker
How long do people wait on a GitHub repository before asking “any update?”, and how often do they hear back? Enter any public repository to see.
Issues with an “any update?” comment
Median wait before asking
No maintainer reply after asking
Had to ask more than once
Open source maintainers are often volunteers. These numbers describe how visible progress is to the people waiting, not how hard anyone works.
If your customers ask the same question, the fix is the same: let them see progress without asking. Vi tells customers automatically when their request is done. See how it works
How it works
- The checker asks GitHub's public API how many issues the repository has, and how many of them have a comment containing “any update”.
- It then reads the comments on the 30 most recent of those issues and finds the first “any update?”, “any news?” or “any progress?” question in each, skipping questions written by the maintainers themselves.
- For each question it measures how many days had passed since the issue was opened and whether a maintainer (owner, member or collaborator) replied afterwards. Everything runs in your browser; nothing is sent to Vi.
What the numbers mean
“Any update?” is what people write when they can't see where something stands. In our study of 897 such questions on GitHub issues from 2025, people waited a median of 38 days before asking, and 60% got no reply from a maintainer afterwards.
A slower or quieter repository is not a worse one. But if a project wants fewer of these questions, the usual answer is to make progress visible: link pull requests to issues, use labels such as “planned” or “in progress”, and leave a short note when plans change.
Read the full studyQuestions
What does the Any Update? Checker measure?
It measures how often people ask “any update?” on a GitHub repository's issues, how long they waited before asking, how often a maintainer replied afterwards, and how often people had to ask more than once.
Does it use the same method as the study?
Yes. It counts comments containing “any update”, “any updates”, “any news” or “any progress”, ignores questions written by maintainers, and treats GitHub's owner, member and collaborator roles as maintainers. People who triage issues without one of those roles are not counted as maintainers, so the reply rate it shows can be slightly lower than the real one.
Why does it read only 30 issues?
GitHub allows about 60 anonymous requests per hour from each visitor, so the checker reads the 30 most recent issues that contain the question. For large repositories the numbers are an estimate, not a full count.
Is my data or the repository's data stored anywhere?
No. The checker runs in your browser and talks to GitHub's public API directly, so Vi's servers never see the repository or the results. Your browser keeps each result for 24 hours so that checking the same repository again does not use your GitHub limit.
Does it work with private repositories?
No. It only works with public repositories, because it uses GitHub's API without signing in.
Customers asking “any update?”
Vi connects customer requests to your team's workflow and tells customers automatically when their request is done, with a status link they can open at any time.
From customer request to code