Discofork
Repository brief

getsentry/sentry

Read the upstream summary on the left, browse the cached forks below it, and load each fork comparison into the right-hand panel.

Cached analysis
cached 2026-03-30T15:34:47.690Z
1mo ago

getsentry/sentry

getsentry/sentry is the main open source Sentry application: a large, actively maintained developer-first error tracking and performance monitoring platform. It is not archived, has high community adoption (43,466 stars, 4,642 forks), and shows very recent activity on March 30, 2026. The repo combines a TypeScript/Node.js frontend with a Python backend and a substantial test/build toolchain.

GitHub
Loading tags...
Stars43,466
Forks4,642
Default branchmaster
Last pushed2026-03-30T15:32:19Z
Recommended shortcuts

Jump straight into Discofork's strongest cached fork picks, or open a compare view in one click.

Forks

Choose a fork to inspect

10 of 10 fork briefs
Selected

Adopt only for legacy compatibility or historical interest. For new work, the fork is far too stale and far behind upstream to be a practical starting point.

Choose this fork only if you specifically want the 2023-era behavior and its profiling/dynamic-sampling experiments. For most adopters, upstream is the better choice because this fork is stale and materially behind current Sentry.

Choose this fork only if you want a legacy, heavily diverged Sentry baseline and can live without modern upstream features. For a production self-hosted observability platform, upstream is the clear choice.

Prefer this fork only for legacy Django exception-logging on old stacks. For any new deployment or active observability use, upstream getsentry/sentry is the clear choice.

Prefer upstream unless you specifically need this fork’s older, customized baseline. This fork looks best for adopters who want to own a frozen variant and can tolerate significant maintenance debt; everyone else should avoid it and stay on active upstream.

Choose this fork only if you need the historical Django exception-logging behavior and can tolerate an abandoned, highly divergent codebase. Most adopters should prefer upstream Sentry unless they are maintaining legacy systems that depend on this older API and workflow.

Prefer upstream unless you specifically need this fork's older base and custom workflow/agent scaffolding. For most adopters, the stale state and large divergence are a liability; the main reason to choose it is if your project is built around its custom internal automation rather than current Sentry features.

Choose this fork only if you need a frozen legacy Sentry variant with specific historical API/CORS behavior. For almost everyone else, upstream is the better base because it is actively maintained and far more capable.

Choose this fork only if you specifically need the old Django exception-logging workflow and can live with a stale, highly divergent codebase. For most adopters, upstream Sentry is the better choice.

Prefer this fork only if you specifically want the legacy Django exception-logging product and accept missing modern Sentry capabilities. For most adopters, upstream is the better choice.