sentry: error tracking that started in 2010

TL;DR: Sentry is developer-first error tracking and performance monitoring, created in 2010 and still pushed daily with 45,038 stars. Its GitHub license field returns NOASSERTION, which is the first thing to check if you plan to self-host it.

An old repository on today’s trending page

Most of this morning’s trending list is eight months old or younger. Sentry was created on 2010-08-30, which makes it the outlier by a wide margin, and it was pushed today.

That combination is the interesting part. A sixteen-year-old project trending alongside new agent tooling usually means one of two things: a breaking change, a major release, or an acquisition. The repository metadata alone does not say which, and the honest answer is that you should read the release notes rather than infer it from a trending rank.

Field	Value
Created	2010-08-30
Last push	2026-10-03
Language	Python
Stars	45,038
Forks	4,892
Open issues	2,273
License field	NOASSERTION
Topics	apm, crash-reporting, crash-reports, csp-report, devops

The license field is the thing to check

The SPDX identifier comes back as NOASSERTION, which means GitHub’s license detection did not match this repository to a license it recognizes in its list.

That is not a red flag on its own. Detection fails for a specific reason: the repository’s license file is either a modified license rather than a standard one, or the project ships components under different terms that cannot be summarized by a single identifier. A project with sixteen years of history and both a server and client SDK is exactly the shape that produces this result.

If you intend to run Sentry yourself, the answer is in the LICENSE files in the repository, per component, not in the API field. Do not infer terms from the star count, and do not infer them from a badge either.

What the topics tell you

The five declared topics are apm, crash-reporting, crash-reports, csp-report, and devops. Four of the five are about catching things going wrong at runtime, and the fifth, csp-report, is about browser security policy violations.

csp-report is the topic that has aged the most interestingly. Content Security Policy reporting was a niche concern for years and became a standard part of how you detect injection attempts in a browser context. If the topic is still being maintained, the browser-side reporting pipeline is still an active surface, which matters if you run agents that browse or generate markup.

apm plus crash reporting in one product is the other signal. Those were two separate purchases for most teams a decade ago.

How to assess it for a self-hosted setup

Start from the project page, which is the canonical source for install and upgrade guidance, then confirm the repository facts directly:

gh api repos/getsentry/sentry \
  --jq '{created: .created_at, pushed: .pushed_at,
         stars: .stargazers_count, open_issues: .open_issues_count,
         license: .license.spdx_id}'

gh api repos/getsentry/sentry/license --jq '.license.spdx_id, .name'

The second command is the one that resolves NOASSERTION, because it reads the license file GitHub indexed for the default branch rather than asking it to classify the repository.

Two thousand two hundred seventy-three open issues is a large queue for a project this age, and it is a fair proxy for support load on a self-hosted deployment. Budget for reading release notes on upgrade rather than assuming patch versions are safe.

When to skip it

Skip it if you want a hosted service with a support contract. Sentry is most often consumed as sentry.io, and the hosted product is a different commitment from running the repository yourself. The metadata here describes the code, not the pricing or the SLA.

Skip it if a noisy open issue queue is going to bother you. A self-hosted deployment means you own the upgrade path, and 2,273 open issues is a reasonable proxy for how much of that lands on you.

Source and Accuracy Notes

• Project page: https://github.com/getsentry/sentry
• Source repository: getsentry/sentry (verified via GitHub API html_url)
• License: NOASSERTION as reported by GitHub API license.spdx_id. Actual terms are defined by the LICENSE files in the repository and were not interpreted for this post.
• Stars at time of writing: 45,038