Public record
Software health reportschema 0.15.0 · metrics 2.10.0 · 2026-07-19 13:10 UTC

stayallive / wp-sentry

A (unofficial) WordPress plugin reporting PHP and JavaScript errors to Sentry.

PHPMIT★ 388 stars⑂ 55 forkssince Oct 2016View on GitHub ↗
KindLibraryPluginhow this is determined

stayallive/wp-sentry holds a health index of 57 out of 100, placing it in the Moderate band. It scores highest on Community & Adoption (68/100) and lowest on AI Readiness (15/100). It was last updated 41 days ago. A single contributor accounts for most of its recent work.

57
overall / 100
Moderate

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.

57
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 55 is calibrated to 57 on the published index scale (record calibration 2026-08-02).

Ownership

Alex BoumaPersonal account
283 followers55 public repossince Sep 2011@chieftools

This repository is owned by a personal account. A single-owner project carries more continuity risk than an organization-backed one.

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
Packagiststayallive/wp-sentryv8.11.18,36714341 days agologgingwordpresssentryerror-monitoringcrash-reporting

Metrics by category

Vitality

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

62Moderate · 21% of overall
How it's scored
18/36Push recencylast push 41 days ago
6.2/36Commit cadence9/52 weeks with commits
13.4/18Commit volume30 commits in the last year
10/10OpenSSF Scorecard: Maintained9 commit(s) and 4 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year30
human_commit_share
days_since_last_push41
active_weeks_last_year9
How it's scored
27/27Ships releases100 releases published
36/36Release recencylatest release 41 days ago
19.8/27Release cadencea release every ~59.7 days
0/10OpenSSF Scorecard: Signed-ReleasesProject has not signed or included provenance with any releases.
Inputs used
releases_count100
latest_release_tagv8.11.1
releases_from_tagsno
days_since_latest_release41
mean_days_between_releases59.7

Community & Adoption

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

68Good · 17% of overall
How it's scored
42/60Stars388 stars
14.4/25Forks55 forks
5.3/15Watchers10 watchers
Inputs used
forks55
stars388
watchers10
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

85Excellent
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
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_services
has_pull_request_templateno
How it's scored
52.3/80Monthly downloads8,367 downloads/month across packagist
0/20Registry dependents0 packages depend on it
Inputs used
packagesstayallive/wp-sentry
dependents0
ecosystemspackagist
total_downloads224,517
monthly_downloads8,367
unverified_packages_excluded

Sustainability & Governance

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

64Moderate · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
2/22.5Commit distributiontop contributor authored 91% of commits
13.5/13.5Contributor breadth29 contributors
10/10OpenSSF Scorecard: Contributorsproject has 15 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled29
top_contributor_share0.909
How it's scored
39.8/42Issue resolution95% of issues closed
20/30PR acceptance48/72 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
3/15OpenSSF Scorecard: Code-ReviewFound 6/30 approved changesets -- score normalized to 2
Inputs used
merged_prs48
open_issues8
closed_issues143
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio0.947
closed_unmerged_prs24
first_time_authors_30d
first_time_prs_merged_30d
first_time_prs_decided_30d
Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
10/30Ownership backingpersonal (user) account
0/20Verified domainnot applicable to user accounts
17.6/25Owner reach283 followers of stayallive
24.7/25Track record55 public repos, account ~14 yr old
Inputs used
followers283
owner_typeUser
is_verified
owner_loginstayallive
public_repos55
account_age_days5,406
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable1 package(s) on packagist
35/35Publish recencylatest publish 41 days ago
20/20Version history143 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesstayallive/wp-sentry
ecosystemspackagist
any_deprecatedno
min_days_since_publish41

Engineering Quality

Are baseline engineering and documentation practices in place?

50Moderate · 19% of overall
How it's scored
24/24CI workflows1 workflow(s)
0/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests0 out of 6 merged PRs checked by a CI test -- score normalized to 0
Inputs used
has_ciyes
has_testsno
has_editorconfigno
has_linter_configno
has_precommit_configno

Documentation

90Excellent
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage sitehttps://wordpress.org/plugins/wp-sentry-integration/
10/10Repository description
10/10Topics2 topics
0/10Wiki
Inputs used
topicswordpress-plugin, sentry
has_wikino
homepagehttps://wordpress.org/plugins/wp-sentry-integration/
docs_sitehttps://wordpress.org/plugins/wp-sentry-integration/
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

37Weak · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
2.2/7.5Branch-Protectionbranch protection is not maximal on development and all release branches
0/2.5CI-Tests0 out of 6 merged PRs checked by a CI test -- score normalized to 0
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
1.5/7.5Code-ReviewFound 6/30 approved changesets -- score normalized to 2
2.5/2.5Contributorsproject has 15 contributing companies or organizations
0/10Dangerous-Workflowno data
0/7.5Dependency-Update-Toolno update tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
7.5/7.5Maintained9 commit(s) and 4 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
0/5Security-Policysecurity policy file not detected
0/7.5Signed-ReleasesProject has not signed or included provenance with any releases.
0/7.5Token-Permissionsno data
5.2/7.5Vulnerabilities3 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated14
scorecard_versionv5.5.0
checks_inconclusive4
scorecard_aggregate3.7
Excluded from scoring (no data or not applicable): Dangerous-Workflow, Packaging, Pinned-Dependencies, Token-Permissions. Remaining weights renormalized.

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.

15Critical · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
0/40Legible commit historyno data
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share
agent_instruction_files
agent_instruction_max_bytes
Excluded from scoring (no data or not applicable): Legible commit history. Remaining weights renormalized.
How it's scored
0/18One-command bootstrap
0/22Automated tests
0/11Lint / format config
0/11Static type checking
10/10Reproducible environmentlockfile
0/10Demonstrated agent practiceno data
0/8Automated maintenanceno data
0/10OpenSSF Scorecard: Pinned-Dependenciesno data
Inputs used
has_nixno
has_testsno
lockfilescomposer.lock
has_dockerfileno
typed_languageno
bootstrap_files
has_devcontainerno
has_linter_configno
typecheck_configs
agent_commit_share
toolchain_manifests
dependency_bot_commit_share
Excluded from scoring (no data or not applicable): Demonstrated agent practice, Automated maintenance, OpenSSF Scorecard: Pinned-Dependencies. Remaining weights renormalized.
How it's scored
0/45Type-checkable codePHP without a type-check config
47.1/55Manageable file sizes4/28 source files over 60KB
Inputs used
primary_languagePHP
largest_source_bytes232,570
source_files_sampled28
oversized_source_files4

Key facts

388GitHub stars
29contributors
30commits, last 12 months
41days since last push
100releases
1bus factor
8open issues
Packagistpackage ecosystems

More detail

OpenSSF Scorecard 3.7 / 10
3.7aggregate

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-07-19 13:09 UTC

10Binary-Artifactsno binaries found in the repo
3Branch-Protectionbranch protection is not maximal on development and all release branches
0CI-Tests0 out of 6 merged PRs checked by a CI test -- score normalized to 0
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
2Code-ReviewFound 6/30 approved changesets -- score normalized to 2
10Contributorsproject has 15 contributing companies or organizations
n/aDangerous-Workflowno workflows found
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained9 commit(s) and 4 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
0Security-Policysecurity policy file not detected
0Signed-ReleasesProject has not signed or included provenance with any releases.
n/aToken-PermissionsNo tokens found
7Vulnerabilities3 existing vulnerabilities detected
Direct dependencies 2
RegistryPackageVersion constraintManifest
Packagistsentry/sentry^4.18.1composer.json
Packagistjean85/pretty-package-versions^1.5composer.json
All dependencies 13

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

RegistryPackageVersionRelation
Packagistjean85/pretty-package-versions1.6.0direct
Packagistsentry/sentry4.18.1direct
Packagistcomposer/installers2.3.0indirect
Packagistcomposer/package-versions-deprecated1.11.99.5indirect
Packagistguzzlehttp/psr72.8.0indirect
Packagistpsr/http-factory1.1.0indirect
Packagistpsr/http-message2.0indirect
Packagistpsr/log1.1.4indirect
Packagistralouphie/getallheaders3.0.3indirect
Packagistsymfony/deprecation-contracts2.5.4indirect
Packagistsymfony/options-resolver5.4.45indirect
Packagistsymfony/polyfill-php731.33.0indirect
Packagistsymfony/polyfill-php801.33.0indirect
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.15.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statisticsPackagist.