getsentry/sentry

Developer-first error tracking and performance monitoring

45.6k stars · 4.9k forks · Python

Healthy

Healthy: actively maintained by 66 people, no known risks.

Why

No rule fired.

What would change this

Maintenance

Partial

Active

Human commits, 30 days
2k
Human commits, 90 days
4.7k
Human commits, 365 days
17k
Bot share of commits, 365 days
13%
Last commit
Oct 14, 2026 (16 hours ago)
Last human commit
Oct 14, 2026 (16 hours ago)
Authors, 90 days
66
Last release
Oct 6, 2026 (8 days ago)
Median PR merge time
under an hour

Responsiveness: of 28 recent issues, 36% got a maintainer reply. Median first response: 3 days.

Sources: Commits, Releases, Merged pull requests, Issues

People

Complete
Owner
Organization
Commits sampled
434 since Oct 14, 2025
Authors for half of commits
11
Authors for 80% of commits
22
Contributors
355

Top committers

Sources: Commits, Contributors

Stars

Complete

Organic, confidence high

Stars per week, 2010-08-29 to 2026-10-11. 14 weeks overlap a burst.Peak 401 a week2010-08-292026-10-11
Bars show stars gained each week. Orange bars overlap a burst.

Bursts

Anyone can buy stars for any repo; bursts alone don't prove the owner did.

Sources: How star history is analyzed

Risk

Complete

Flags

No risk flags.

License

Now
FSL-1.1 (not OSI-approved)
A year ago
FSL-1.1 (not OSI-approved)

Packages

No published packages found.

OpenSSF Scorecard: 6.7 out of 10 (via deps.dev).

Sources: GitHub: getsentry/sentry

Badge

Add this to a README to show the current verdict:

[![RepoRadar](https://reporadar.ai/getsentry/sentry/badge.svg)](https://reporadar.ai/getsentry/sentry)

Earlier verdicts

Computed 15 hours ago · method 2026.10.2