getsentry/sentry

Developer-first error tracking and performance monitoring

46k stars5kforks1.6kissuespushed

sentry.io ↗github.com/getsentry/sentry ↗

Example reportsign inexamples

Not enough evidence.

There's too little to go on.

  • Before writing code, open an issue and ask whether a pull request would be welcome.

Only 5 pull requests from outside contributors have had time for an answer, and 4 of them got no reply. That's too few to say the project ignores outside work.

Data until 10 Nov 2026 · checked

How this was counted
What Holt read
Holt read the 400 most recent pull requests on this repo, opened between 23 Oct 2026 and 9 Nov 2026. 5 came from people outside the team, like you, and had been open long enough to get an answer. Those are the ones that show how newcomers are treated.
Words used here
A pull request (PR) is a change you propose to a project. Merged means the maintainers accepted it. An outsider is anyone who isn't on the project's team, like you.
What we read
400 pull requests on GitHub, opened 23 Oct – 9 Nov 2026.
The team and outside contributors
236 of them came from 58 people on the project's team and are left out. The team is everyone GitHub shows as an owner, member or collaborator, plus anyone the history shows merging, closing or formally reviewing other people's pull requests. Everyone else is an outside contributor, including people who come back.
Bots
151 pull requests opened by bots (dependency updates and the like) are left out. Only a maintainer's reply counts as a reply: not a bot, a CLA check, the author, or a passer-by.
Drafts and spam
5 pull requests from outside contributors were drafts or were marked as spam or invalid, so they aren't counted anywhere.
Too recent to count
3 pull requests from outside contributors were opened in the last 14 days, too recently to know how they will end, so they aren't counted yet.
Closed without a word
1 pull request from an outside contributor was closed without a reply. That's often how maintainers clear out spam, so it isn't counted as ignored.
What decided it
Only 5 pull requests from outside contributors have had time for an answer, and 4 of them got no reply. That's too few to say the project ignores outside work.
The rule
Only pull requests from outside contributors opened between 14 days and a year ago count, so each has had time for an answer and reflects how the project works now. “Worth your time” needs at least 2 of them merged, from at least 2 different people, with at least 3 in 10 people getting their first pull request merged (once 8 or more have tried), at least 1 in 10 merged, no more than half left without any reply, a typical first reply within 3 weeks, and people actually reviewing what gets merged. “Long shot” is a project that merges some outside work but misses one of those: fewer than 3 in 10 newcomers getting in, fewer than 1 in 10 merged, most left unanswered, very slow first replies, or only one person's work getting in. “Not worth your time” is an archived repository, a mirror, a project with nothing merged or pushed in 90 days, merges nobody reviews, fewer than 1 in 20 outside pull requests merged once at least 20 have been decided, or outside pull requests that are almost all ignored. “Personal project” is someone's own project or a small team's, like a hackathon entry, with nothing from outside ever merged. “A list, not code” is a list or a catalogue of entries, like links or package listings, where a merged entry isn't code work. Anything in between is “Not enough evidence”. These rules are fixed; no AI chooses the verdict.
What Holt couldn't check

No AI read the conversations for this report, so it doesn't say how maintainers talk to newcomers or what kind of project this is. The verdict and the numbers are counted straight from GitHub and don't need an AI.

Find a Python project with a track record

What happened to outside pull requests

  • 1closed without a word
  • 4got no reply
  • 0 of 5

    outside PRs merged (0%)

  • No replies

    to measure: no outside PR got an answer

  • 0

    people got their first PR merged here

  • 80%

    of outside PRs sat open with no reply (4)

  • 20%

    of outside PRs were closed without a word (1)

  • 5

    different outsiders tried recently

README and contributing guide

Sentry

Users and logs provide clues. Sentry provides answers.

What's Sentry?

Sentry is the debugging platform that helps every developer detect, trace, and fix issues. Code breaks, fix it faster.

Official Sentry SDKs

JavaScript Electron React Native Python Ruby PHP Laravel Go Rust Java / Kotlin Objective-C / Swift C# / F# C / C++ Dart / Flutter Perl Clojure Elixir Unity Unreal Engine Godot Engine PowerShell

Resources

More about this project · numbers, languages, contributors

Statistics

Stars
46k
Forks
5k
Contributors
1.1k
Open issues
1.6k
Open PRs
645
Created
30 Aug 2010
Licence
Other
Default branch
master

What you'd need to know

  • Python57%
  • TypeScript42%
  • MDX1%

Topics

  • crash-reporting
  • crash-reports
  • error-monitoring
  • monitoring
  • devops
  • csp-report
  • django
  • error-logging
  • sentry
  • python
  • monitor
  • apm

Was this verdict right?

Know this project? Tell us. It helps us get verdicts right.

Maintainer of this repo?

See what would earn it a Holt badge. Get a badge →