Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-08-27 16:56 UTC

getsentry / sentry-php

The official PHP SDK for Sentry (sentry.io)

PHPMIT★ 1,913 stars⑂ 474 forkssince Jan 2012View on GitHub ↗

getsentry/sentry-php holds a health index of 34 out of 100, placing it in the At Risk band. It scores highest on Vitality (94/100) and lowest on Security (47/100). It was last updated today. 3 contributors account for most of its recent work.

34
overall / 100
At Risk

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.

34
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 81 is calibrated to 94 on the published index scale (record calibration 2026-08-02). High-Risk Jurisdiction Policy applies a 50% multiplier to weighted overall health and gives it an At Risk ceiling of 34.

Ownership

SentryOrganization · verified domain
3,168 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 publishTags
Packagistsentry/sentry4.31.07,996,1381740 days agologloggingprofilingsentryerror-handlertracingerror-monitoringcrash-reportingcrash-reports

Metrics by category

Vitality

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

94Exceptional · 21% of overall
How it's scored
36/36Push recencylast push 0 days ago
26.3/36Commit cadence38/52 weeks with commits
18/18Commit volume209 commits in the last year
10/10OpenSSF Scorecard: Maintained30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year209
human_commit_share0.57
days_since_last_push0
active_weeks_last_year38

Release discipline

100Exceptional
How it's scored
27/27Ships releases100 releases published
36/36Release recencylatest release 0 days ago
27/27Release cadencea release every ~17.4 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count100
latest_release_tag4.31.0
releases_from_tagsno
days_since_latest_release0
mean_days_between_releases17.4
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Signed-Releases. Remaining weights renormalized.

Community & Adoption

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

91Excellent · 17% of overall
How it's scored
53.2/60Stars1,913 stars
22.3/25Forks474 forks
10.7/15Watchers84 watchers
Inputs used
forks474
stars1,913
watchers84
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

92Excellent
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (MIT)
18/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges10
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_servicesgithub.com, poser.pugx.org, shields.io
has_pull_request_templateyes
How it's scored
80/80Monthly downloads7,996,138 downloads/month across packagist
16.6/20Registry dependents311 packages depend on it
Inputs used
packagessentry/sentry
dependents311
ecosystemspackagist
total_downloads261,529,920
monthly_downloads7,996,138
unverified_packages_excluded

Sustainability & Governance

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

88Excellent · 23% of overall
How it's scored
36/54Bus factor3 contributor(s) cover half of all commits
15/22.5Commit distributiontop contributor authored 33% of commits
13.5/13.5Contributor breadth98 contributors
10/10OpenSSF Scorecard: Contributorsproject has 57 contributing companies or organizations
Inputs used
bus_factor3
contributors_sampled98
top_contributor_share0.332
How it's scored
40.8/42Issue resolution97% of issues closed
25/30PR acceptance1,171/1,408 decided PRs merged
7.8/13Newcomer PR acceptance3/5 first-time contributors' PRs merged in 30d
10.5/15OpenSSF Scorecard: Code-ReviewFound 17/23 approved changesets -- score normalized to 7
Inputs used
merged_prs1,171
open_issues20
closed_issues696
prs_merged_7d5
prs_decided_7d5
prs_merged_30d8
prs_decided_30d10
issue_closed_ratio0.972
closed_unmerged_prs237
first_time_authors_30d5
first_time_prs_merged_30d3
first_time_prs_decided_30d5
How it's scored
30/30Ownership backingorganization-owned
20/20Verified domain
25/25Owner reach3,168 followers of getsentry
25/25Track record802 public repos, account ~14 yr old
Inputs used
followers3,168
owner_typeOrganization
is_verifiedyes
owner_logingetsentry
public_repos802
account_age_days5,321

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable1 package(s) on packagist
35/35Publish recencylatest publish 0 days ago
20/20Version history174 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagessentry/sentry
ecosystemspackagist
any_deprecatedno
min_days_since_publish0

Engineering Quality

Are baseline engineering and documentation practices in place?

80Excellent · 19% of overall
How it's scored
24/24CI workflows4 workflow(s)
24/24Tests present
16/16Linter config.php-cs-fixer.dist.php, phpstan.neon
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests24 out of 24 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigyes
has_linter_configyes
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage sitehttps://sentry.io
10/10Repository description
10/10Topics11 topics
0/10Wiki
Inputs used
topicsphp, error-monitoring, error-handler, crash-reporting, crash-reports, sentry, sentry-client, hacktoberfest, tag-production, 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?

47Weak · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
3/7.5Branch-Protectionbranch protection is not maximal on development and all release branches
2.5/2.5CI-Tests24 out of 24 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
5.2/7.5Code-ReviewFound 17/23 approved changesets -- score normalized to 7
2.5/2.5Contributorsproject has 57 contributing companies or organizations
0/10Dangerous-Workflowno data
7.5/7.5Dependency-Update-Toolupdate tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
7.5/7.5Maintained30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
0/5Packagingno data
0/5Pinned-Dependenciesno data
0/5SASTSAST tool is not run on all commits -- score normalized to 0
5/5Security-Policysecurity policy file detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsno data
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated13
scorecard_versionv5.5.0
checks_inconclusive5
scorecard_aggregate7.2
high_risk_jurisdiction_cap34
high_risk_jurisdiction_multiplier50
security_posture_after_multiplier36
security_posture_before_jurisdiction72
Excluded from scoring (no data or not applicable): Dangerous-Workflow, Packaging, Pinned-Dependencies, Signed-Releases, Token-Permissions. Remaining weights renormalized. High-Risk Jurisdiction Policy applies a 50% multiplier and gives Security posture an At risk ceiling of 34.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisoriesno direct dependency carries a known advisory
0/25Indirect dependencies free of known advisoriestransitive set not separable from development and test dependencies in this scope
0/40No advisories left outstandingno advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages1
unassessed_packages22
affected_by_severitynone
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 1 resolved dependencies against OSV. 22 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list. 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.

70Good · 4% of overall
How it's scored
45/45Agent instructionsAGENTS.md, CLAUDE.md
15/15Machine-readable docs (llms.txt)llms.txt served by the project website (https://sentry.io/llms.txt)
40/40Legible commit history57 of 57 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://sentry.io/llms.txt
legible_history_share1
agent_instruction_filesAGENTS.md, CLAUDE.md
agent_instruction_max_bytes5,820
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config.php-cs-fixer.dist.php, phpstan.neon
0/11Static type checking
0/10Reproducible environment
8/10Demonstrated agent practice4 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance35 of the last 100 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependenciesno data
Inputs used
has_nixno
has_testsyes
lockfiles
has_dockerfileno
typed_languageno
bootstrap_files
has_devcontainerno
has_linter_configyes
typecheck_configs
agent_commit_share0.04
toolchain_manifests
dependency_bot_commit_share0.35
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Pinned-Dependencies. Remaining weights renormalized.
How it's scored
0/45Type-checkable codePHP without a type-check config
55/55Manageable file sizes0/257 source files over 60KB
Inputs used
primary_languagePHP
largest_source_bytes51,167
source_files_sampled257
oversized_source_files0

Key facts

1,913GitHub stars
98contributors
209commits, last 12 months
0days since last push
100releases
3bus factor
20open issues
Packagistpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token

More detail

Star and fork history 0 ★ / 474 ⇿
0Stars
474Forks
99Releases

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.

010020030040050046392012-022019-052026-08
Major 2Minor 53Patch 43

Each point covers 14 days.

OpenSSF Scorecard 7.2 / 10
7.2aggregate

Independent, tool-agnostic security assessment from the open-source OpenSSF Scorecard. Each check rewards a security practice, not a specific vendor's tool. Checks Scorecard could not determine are marked n/a and excluded from the security score (never counted as zero).Scorecard v5.5.0 · 2026-08-27 16:56 UTC

10Binary-Artifactsno binaries found in the repo
4Branch-Protectionbranch protection is not maximal on development and all release branches
10CI-Tests24 out of 24 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
7Code-ReviewFound 17/23 approved changesets -- score normalized to 7
10Contributorsproject has 57 contributing companies or organizations
n/aDangerous-Workflowno workflows found
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
n/aPinned-Dependenciesno dependencies found
0SASTSAST tool is not run on all commits -- score normalized to 0
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
n/aToken-PermissionsNo tokens found
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 4
RegistryPackageVersion constraintManifest
Packagistguzzlehttp/psr7^1.8.4|^2.1.1|^3.0.0composer.json
Packagistjean85/pretty-package-versions^1.5|^2.0.4composer.json
Packagistpsr/log^1.0|^2.0|^3.0composer.json
Packagistsymfony/options-resolver^4.4.30|^5.0.11|^6.0|^7.0|^8.0composer.json
All dependencies 23

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

RegistryPackageVersionRelation
Packagistguzzlehttp/psr7direct
Packagistjean85/pretty-package-versionsdirect
Packagistpsr/logdirect
Packagistsymfony/options-resolverdirect
Packagistcarthage-software/mago1.30.0indirect
Packagistext-curlindirect
Packagistext-jsonindirect
Packagistext-mbstringindirect
Packagistfriendsofphp/php-cs-fixerindirect
Packagistguzzlehttp/guzzleindirect
Packagistguzzlehttp/promisesindirect
Packagistmonolog/monologindirect
Packagistnyholm/psr7indirect
Packagistopen-telemetry/apiindirect
Packagistopen-telemetry/contextindirect
Packagistopen-telemetry/exporter-otlpindirect
Packagistopen-telemetry/sdkindirect
Packagistopen-telemetry/sem-convindirect
Packagistphpindirect
Packagistphpstan/phpstanindirect
Packagistphpunit/phpunitindirect
Packagistspiral/roadrunner-httpindirect
Packagistspiral/roadrunner-workerindirect
Dependency advisories 0

This repository publishes no package the index resolves, so its own dependency graph was assessed — 1 packages, which also include development and test pins that never ship: 0 carry known advisories, of which 0 are direct. 22 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list.

No known advisories affect the assessed dependencies.

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 statisticsPackagist.