getsentry/sentryDeveloper-first error tracking and performance monitoring
Developer-first error tracking and performance monitoring
licence Othersince 2010branch mastersentry.io ↗github.com/getsentry/sentry ↗
Example reportSign in to check any repo you like.sign inmore examples
Only 2 pull requests from outside contributors have had time for an answer, and 2 of them got no reply. That's too few to say the project ignores outside work.
Of 2 pull requests from outside contributors (14 Sep – 29 Sep 2026) that have had time for an answer, 0 were merged (0%). No maintainer replied to any of them. 100% sat open with no reply. Another 5 were opened in the last 14 days, too recently to count.
Nobody got their first pull request merged here in this period.
There's too little to go on. Before writing code, open an issue and ask whether a pull request would be welcome.
data until 30 Sept 2026 · checked
Developer-first error tracking and performance monitoring Users and logs provide clues.
Looking for somewhere friendlier to start?
[ find a welcoming project → ]0 of 2
outside PRs merged (0%)
No replies
to measure: no outside PR got an answer
0
people got their first PR merged here
100%
of outside PRs sat open with no reply (2)
0%
of outside PRs were closed without a word (0)
2
different outsiders tried recently
Holt didn't see enough outside work to map where it lands.
Know this project? Tell us. It helps us get verdicts right.
Outside contributor's pull request #124397 had no reply from anyone when we looked: “fix(crons): Make CheckInTimeline same-day check timezone-aware”
Outside contributor's pull request #124393 had no reply from anyone when we looked: “fix(postgres): Sanitize strings in array query parameters”
Merge plan ✦
Your first pull request as steps, what gets merged, and why outside ones get closed, in the maintainers' words.
Maintainer of this repo?
See what would earn it a Holt badge. Get a badge →
Nobody on it yet
What to do next: Read the comments first, then ask if it's still free for you to take.
2 open pull requests
What to do next: Look at the open pull request first; if it has stalled, ask to take over.
2 open pull requests
What to do next: Look at the open pull request first; if it has stalled, ask to take over.
2 open pull requests
What to do next: Look at the open pull request first; if it has stalled, ask to take over.