Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-09 15:02 UTC

getsentry / sentry-elixir

The official Elixir SDK for Sentry (sentry.io)

ElixirMIT★ 694 stars⑂ 216 forkssince Aug 2014View on GitHub ↗
KindLibraryNetwork servicehow this is determined

getsentry/sentry-elixir holds a health index of 86 out of 100, placing it in the Excellent band. It scores highest on Vitality (95/100) and lowest on Security (21/100). It was last updated today. A single contributor accounts for most of its recent work.

86
overall / 100
Excellent

Software health index

Metrics are grouped into weighted categories on one standardized 1–100 scale. Overall starts as their weighted mean, calibrated against the distribution of the public record so bands carry percentile meaning; when public evidence triggers the High-Risk Jurisdiction Policy, the rating is adjusted and receives an At Risk ceiling of 34.

86
Exceptional93-100The record's top tier (≈ top 5%); essentially all checked criteria met
Excellent80-92Strong across the board; minor gaps
Good65-79Healthy; gaps are limited and manageable
Moderate50-64Acceptable with notable gaps; review recommended
Weak35-49Material weaknesses across several areas
At Risk20-34Significant weaknesses; adoption warrants caution
Critical1-19Severe problems (abandoned, single-maintainer, no hygiene)
VitalityCommunity &AdoptionSustainability &GovernanceEngineeringQualitySecurityAI Readiness

Score profile

Each axis is a category. The shape matters more than the average — a healthy subject fills the whole shape, while a spike-and-crater profile means strength in one dimension is masking risk in another.

The weighted overall 72 is calibrated to 86 on the published index scale (record calibration 2026-08-02).

Ownership

SentryOrganization · verified domain
3,188 followers802 public repossince Feb 2012

This repository is backed by an organization — shared, accountable stewardship that can outlive any single maintainer.

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
Hexsentry13.5.1477,1581047 days ago

Metrics by category

Vitality

Is the project alive — is code being written and are releases shipping?

95Exceptional · 21% of overall
How it's scored
36/36Push recency — last push 0 days ago
29.1/36Commit cadence — 42/52 weeks with commits
18/18Commit volume — 193 commits in the last year
0/10OpenSSF Scorecard: Maintained — no data
Inputs used
commits_last_year193
human_commit_share0.79
days_since_last_push0
active_weeks_last_year42

Release discipline

100Exceptional
How it's scored
27/27Ships releases — 91 releases published
36/36Release recency — latest release 7 days ago
27/27Release cadence — a release every ~14.2 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count91
latest_release_tag13.5.1
releases_from_tagsno
days_since_latest_release7
mean_days_between_releases14.2

Community & Adoption

Does the project have users, downloads, attention, and a welcoming setup for contributors?

88Excellent · 17% of overall
How it's scored
46.1/60Stars — 694 stars
19.4/25Forks — 216 forks
6.7/15Watchers — 17 watchers
Inputs used
forks216
stars694
watchers17
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

100Exceptional
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (MIT)
18/18CONTRIBUTING guide
13.5/13.5Code of conduct
7.2/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges8
has_contributingyes
has_issue_templateyes
has_code_of_conductyes
readme_badge_servicesgithub.com, shields.io
has_pull_request_templateyes
How it's scored
75.7/80Monthly downloads — 477,158 downloads/month across hex
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagessentry
dependents—
ecosystemshex
total_downloads75,820,368
monthly_downloads477,158
unverified_packages_excluded—
Excluded from scoring (no data or not applicable): Registry dependents. Remaining weights renormalized.

Sustainability & Governance

Will the project survive its people — bus factor, responsiveness, who backs it, and package upkeep?

79Good · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
10.5/22.5Commit distribution — top contributor authored 54% of commits
13.5/13.5Contributor breadth — 98 contributors
0/10OpenSSF Scorecard: Contributors — no data
Inputs used
bus_factor1
contributors_sampled98
top_contributor_share0.535
How it's scored
41.1/42Issue resolution — 98% of issues closed
25.9/30PR acceptance — 614/711 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — no data
Inputs used
merged_prs614
open_issues10
closed_issues444
prs_merged_7d1
prs_decided_7d1
prs_merged_30d10
prs_decided_30d13
issue_closed_ratio0.978
closed_unmerged_prs97
first_time_authors_30d0
first_time_prs_merged_30d0
first_time_prs_decided_30d0
Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
30/30Ownership backing — organization-owned
20/20Verified domain
25/25Owner reach — 3,188 followers of getsentry
25/25Track record — 802 public repos, account ~14 yr old
Inputs used
followers3,188
owner_typeOrganization
is_verifiedyes
owner_logingetsentry
public_repos802
account_age_days5,334

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on hex
35/35Publish recency — latest publish 7 days ago
20/20Version history — 104 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagessentry
ecosystemshex
any_deprecatedno
min_days_since_publish7

Engineering Quality

Are baseline engineering and documentation practices in place?

62Moderate · 19% of overall
How it's scored
24/24CI workflows — 5 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests — no data
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage site — https://sentry.io
10/10Repository description
10/10Topics — 4 topics
0/10Wiki
Inputs used
topicstag-production, hacktoberfest, team-web-backend, sdk
has_wikino
homepagehttps://sentry.io
docs_sitehttps://sentry.io
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

Are visible security and supply-chain practices strong, without unresolved high-risk jurisdiction exposure?

21At Risk · 16% of overall
How it's scored
0/30Security policy (SECURITY.md)
0/25Dependabot config
0/25Dependency lockfiles — published library — lockfiles are an application concern, not expected
0/20CodeQL workflow
Inputs used
sourcefile_signals
lockfilesmix.lock, package-lock.json
manifestsmix.exs
has_codeql_workflowno
has_security_policyno
has_dependabot_configno
Excluded from scoring (no data or not applicable): Dependency lockfiles. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisories — no direct dependency carries a known advisory
0/25Indirect dependencies free of known advisories — transitive set not separable from development and test dependencies in this scope
0/40No advisories left outstanding — no advisory carries a publication date
Inputs used
sourceosv
advisories1
affected_packages1
assessed_packages84
unassessed_packages0
affected_by_severityhigh 1
direct_affected_packages0
Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories, No advisories left outstanding. Remaining weights renormalized. Matched 84 resolved dependencies against OSV. This repository publishes no package the index resolves, so the repository dependency graph was assessed instead. That graph mixes development and test pins with shipped dependencies, so only the declared runtime dependencies are scored; transitive findings are reported as context and excluded from the score. Reachability is not analyzed.

AI Readiness

How well is the repo equipped to be developed and maintained with AI coding agents? Carries a deliberately small weight (4%): agent tooling is a real maintenance signal, but a repository with none can still reach 100/100.

88Excellent · 4% of overall
How it's scored
45/45Agent instructions — AGENTS.md, CLAUDE.md
15/15Machine-readable docs (llms.txt) — llms.txt served by the project website (https://sentry.io/llms.txt)
40/40Legible commit history — 77 of 79 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://sentry.io/llms.txt
legible_history_share0.975
agent_instruction_filesAGENTS.md, CLAUDE.md
agent_instruction_max_bytes6,813
How it's scored
12.6/18One-command bootstrap — mix.exs, test_integrations/legacy_otel/mix.exs, test_integrations/phoenix_app/mix.exs (toolchain convention, no task runner)
22/22Automated tests
0/11Lint / format config
11/11Static type checking — test_integrations/tracing/tsconfig.json
10/10Reproducible environment — lockfile
10/10Demonstrated agent practice — 6 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance — 5 of the last 100 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependencies — no data
Inputs used
has_nixno
has_testsyes
lockfilesmix.lock, package-lock.json
has_dockerfileno
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configstest_integrations/tracing/tsconfig.json
agent_commit_share0.06
toolchain_manifestsmix.exs, test_integrations/legacy_otel/mix.exs, test_integrations/phoenix_app/mix.exs, test_integrations/prod_mode/mix.exs, test_integrations/umbrella/apps/admin/mix.exs, test_integrations/umbrella/apps/public/mix.exs, test_integrations/umbrella/mix.exs
dependency_bot_commit_share0.05
How it's scored
27/45Type-checkable code — Elixir with type-check config (test_integrations/tracing/tsconfig.json)
55/55Manageable file sizes — 0/243 source files over 60KB
Inputs used
primary_languageElixir
largest_source_bytes57,335
source_files_sampled243
oversized_source_files0

Key facts

694GitHub stars
98contributors
193commits, last 12 months
0days since last push
91releases
1bus factor
10open issues
Hexpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • OpenSSF Scorecard did not return a usable result (exit code 0; Skipping github.com/getsentry/sentry-elixir: run: internal error: ListCommits:error during graphqlHandler.setup: internal error: githubv4.Query: Something went wrong while executing your query on 2026-09-09T15:02:57Z. Please include `A452:1F18CA:4F80AE:4CCFA6:6AA1751F` when reporting this issue.); skipping Scorecard checks

More detail

Star and fork history 0 ★ / 216 ⇿
0Stars
216Forks
86Releases

When each star and fork was added, collected from GitHub and bucketed by day. Cumulative growth sits directly above the daily additions it is made of, so the two read against each other: steady organic accretion looks nothing like an abrupt, short-lived burst. Where that difference is measurable, it is reported as growth authenticity.

0408012016020024020332015-032020-112026-07
Major 12Minor 23Patch 46

Each point covers 11 days.

Direct dependencies 15
RegistryPackageVersion constraintManifest
Hexno_warnplts/dialyzer.pltmix.exs
Hexnimble_options~> 1.0mix.exs
Hexnimble_ownership~> 1.0mix.exs
Hexhackney>= 1.8.0 and < 5.0.0mix.exs
Hexfinch~> 0.21mix.exs
Hexjason~> 1.1mix.exs
Hexphoenix~> 1.6mix.exs
Hexphoenix_live_view~> 0.20 or ~> 1.0mix.exs
Hexplug—mix.exs
Hextelemetry~> 0.4 or ~> 1.0mix.exs
Hexopentelemetry>= 0.0.0mix.exs
Hexopentelemetry_api>= 0.0.0mix.exs
Hexopentelemetry_exporter>= 0.0.0mix.exs
Hexopentelemetry_semantic_conventions>= 0.0.0mix.exs
Hexshutdown—mix.exs
All dependencies 84

Full resolved dependency set from the GitHub dependency graph: 0 direct and 84 indirect (transitive) packages. The transitive closure is complete when the repository commits a lockfile.

RegistryPackageVersionRelation
npm@emnapi/core1.11.1indirect
npm@emnapi/runtime1.11.1indirect
npm@emnapi/wasi-threads1.2.2indirect
npm@jridgewell/gen-mapping0.3.13indirect
npm@jridgewell/remapping2.3.5indirect
npm@jridgewell/resolve-uri3.1.2indirect
npm@jridgewell/sourcemap-codec1.5.5indirect
npm@jridgewell/trace-mapping0.3.31indirect
npm@napi-rs/wasm-runtime1.1.6indirect
npm@oxc-project/types0.137.0indirect
npm@playwright/test1.56.1indirect
npm@rolldown/binding-android-arm641.1.2indirect
npm@rolldown/binding-darwin-arm641.1.2indirect
npm@rolldown/binding-darwin-x641.1.2indirect
npm@rolldown/binding-freebsd-x641.1.2indirect
npm@rolldown/binding-linux-arm-gnueabihf1.1.2indirect
npm@rolldown/binding-linux-arm64-gnu1.1.2indirect
npm@rolldown/binding-linux-arm64-musl1.1.2indirect
npm@rolldown/binding-linux-ppc64-gnu1.1.2indirect
npm@rolldown/binding-linux-s390x-gnu1.1.2indirect
npm@rolldown/binding-linux-x64-gnu1.1.2indirect
npm@rolldown/binding-linux-x64-musl1.1.2indirect
npm@rolldown/binding-openharmony-arm641.1.2indirect
npm@rolldown/binding-wasm32-wasi1.1.2indirect
npm@rolldown/binding-win32-arm64-msvc1.1.2indirect
npm@rolldown/binding-win32-x64-msvc1.1.2indirect
npm@rolldown/pluginutils1.0.1indirect
npm@sentry-internal/browser-utils10.5.0indirect
npm@sentry-internal/feedback10.5.0indirect
npm@sentry-internal/replay10.5.0indirect
npm@sentry-internal/replay-canvas10.5.0indirect
npm@sentry/browser10.5.0indirect
npm@sentry/core10.5.0indirect
npm@sentry/svelte10.5.0indirect
npm@sveltejs/acorn-typescript1.0.9indirect
npm@sveltejs/vite-plugin-svelte7.1.2indirect
npm@tybys/wasm-util0.10.3indirect
npm@types/estree1.0.8indirect
npm@types/node22.19.2indirect
npm@types/trusted-types2.0.7indirect
npmacorn8.16.0indirect
npmaria-query5.3.1indirect
npmaxobject-query4.1.0indirect
npmclsx2.1.1indirect
npmdeepmerge4.3.1indirect
npmdetect-libc2.1.2indirect
npmdevalue5.8.1indirect
npmesm-env1.2.2indirect
npmesrap2.2.8indirect
npmfdir6.5.0indirect
npmfsevents2.3.2indirect
npmfsevents2.3.3indirect
npmis-reference3.0.3indirect
npmlightningcss1.32.0indirect
npmlightningcss-android-arm641.32.0indirect
npmlightningcss-darwin-arm641.32.0indirect
npmlightningcss-darwin-x641.32.0indirect
npmlightningcss-freebsd-x641.32.0indirect
npmlightningcss-linux-arm-gnueabihf1.32.0indirect
npmlightningcss-linux-arm64-gnu1.32.0indirect
npmlightningcss-linux-arm64-musl1.32.0indirect
npmlightningcss-linux-x64-gnu1.32.0indirect
npmlightningcss-linux-x64-musl1.32.0indirect
npmlightningcss-win32-arm64-msvc1.32.0indirect
npmlightningcss-win32-x64-msvc1.32.0indirect
npmlocate-character3.0.0indirect
npmmagic-string0.30.21indirect
npmnanoid3.3.16indirect
npmobug2.1.3indirect
npmpicocolors1.1.1indirect
npmpicomatch4.0.4indirect
npmplaywright1.56.1indirect
npmplaywright-core1.56.1indirect
npmpostcss8.5.25indirect
npmrolldown1.1.2indirect
npmsource-map-js1.2.1indirect
npmsvelte5.55.7indirect
npmtinyglobby0.2.17indirect
npmtslib2.8.1indirect
npmtypescript5.9.3indirect
npmundici-types6.21.0indirect
npmvite8.1.0indirect
npmvitefu1.1.3indirect
npmzimmerframe1.1.4indirect
Dependency advisories 1

This repository publishes no package the index resolves, so its own dependency graph was assessed — 84 packages, which also include development and test pins that never ship: 1 carry known advisories, of which 0 are direct.

PackageVersionRelationSeverityAdvisoriesFixed in
nanoid3.3.16indirecthigh15.1.6

An advisory means the version recorded in the dependency graph falls inside an advisory’s affected range. Reachability is not analysed, and the graph includes development and test pins — a finding may concern tooling rather than shipped software.

Raw JSON report machine-readable

Feedback

Spotted something off in this report, or have thoughts to share? Wrong measurements, missed tooling, ideas, questions — anything is welcome. Every message is read and gets a response.

The message is kept through sign-in.

Scores are signals, not warranties. They reflect publicly visible practices on GitHub — not a code audit, and not a security guarantee.

Missing data is excluded and weights renormalized, never scored as zero. Methodology is versioned and open: metrics v2.10.0, schema v0.34.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statistics — Hex.