Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-13 06:51 UTC

web-push-libs / web-push-php

Web Push library for PHP

PHPMIT★ 1,889 stars⑂ 312 forkssince Nov 2015View on GitHub ↗

web-push-libs/web-push-php holds a health index of 83 out of 100, placing it in the Excellent band. It scores highest on Community & Adoption (85/100) and lowest on AI Readiness (45/100). It was last updated 3 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

WebPush librariesOrganization
191 followers9 public repossince Jun 2016

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
Packagistminishlink/web-pushv11.0.01,734,5475651 days agowebnotificationspushwebpushpush-api

Metrics by category

Vitality

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

73Good · 21% of overall
How it's scored
36/36Push recency — last push 3 days ago
6.9/36Commit cadence — 10/52 weeks with commits
12.7/18Commit volume — 25 commits in the last year
5/10OpenSSF Scorecard: Maintained — 4 commit(s) and 3 issue activity found in the last 90 days -- score normalized to 5
Inputs used
commits_last_year25
human_commit_share0.96
days_since_last_push3
active_weeks_last_year10
How it's scored
27/27Ships releases — 56 releases published
36/36Release recency — latest release 51 days ago
19.8/27Release cadence — a release every ~80.4 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count56
latest_release_tagv11.0.0
releases_from_tagsno
days_since_latest_release51
mean_days_between_releases80.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?

85Excellent · 17% of overall
How it's scored
53.1/60Stars — 1,889 stars
20.8/25Forks — 312 forks
10.7/15Watchers — 84 watchers
Inputs used
forks312
stars1,889
watchers84
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (MIT)
18/18CONTRIBUTING guide
0/13.5Code of conduct
7.2/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges1
has_contributingyes
has_issue_templateyes
has_code_of_conductno
readme_badge_servicesgithub.com
has_pull_request_templateno
How it's scored
80/80Monthly downloads — 1,734,547 downloads/month across packagist
12.7/20Registry dependents — 80 packages depend on it
Inputs used
packagesminishlink/web-push
dependents80
ecosystemspackagist
total_downloads17,945,162
monthly_downloads1,734,547
unverified_packages_excluded—

Sustainability & Governance

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

70Good · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
6.8/22.5Commit distribution — top contributor authored 70% of commits
13.5/13.5Contributor breadth — 40 contributors
10/10OpenSSF Scorecard: Contributors — project has 9 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled40
top_contributor_share0.698
How it's scored
40/42Issue resolution — 95% of issues closed
23.2/30PR acceptance — 126/163 decided PRs merged
13/13Newcomer PR acceptance — 1/1 first-time contributors' PRs merged in 30d
12/15OpenSSF Scorecard: Code-Review — Found 23/28 approved changesets -- score normalized to 8
Inputs used
merged_prs126
open_issues14
closed_issues279
prs_merged_7d1
prs_decided_7d1
prs_merged_30d1
prs_decided_30d1
issue_closed_ratio0.952
closed_unmerged_prs37
first_time_authors_30d1
first_time_prs_merged_30d1
first_time_prs_decided_30d1
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain
16.4/25Owner reach — 191 followers of web-push-libs
19.3/25Track record — 9 public repos, account ~10 yr old
Inputs used
followers191
owner_typeOrganization
is_verifiedno
owner_loginweb-push-libs
public_repos9
account_age_days3,748

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on packagist
35/35Publish recency — latest publish 51 days ago
20/20Version history — 56 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesminishlink/web-push
ecosystemspackagist
any_deprecatedno
min_days_since_publish51

Engineering Quality

Are baseline engineering and documentation practices in place?

66Good · 19% of overall
How it's scored
24/24CI workflows — 1 workflow(s)
24/24Tests present
16/16Linter config — .php-cs-fixer.php, phpstan.neon
0/9.6Pre-commit hooks
0/6.4.editorconfig
12/20OpenSSF Scorecard: CI-Tests — 20 out of 29 merged PRs checked by a CI test -- score normalized to 6
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno

Documentation

50Moderate
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics — 4 topics
0/10Wiki
Inputs used
topicswebpush, notifications, php, push-notifications
has_wikino
homepage—
docs_site—
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

59Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
2.2/7.5Branch-Protection — branch protection is not maximal on development and all release branches
1.5/2.5CI-Tests — 20 out of 29 merged PRs checked by a CI test -- score normalized to 6
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
6/7.5Code-Review — Found 23/28 approved changesets -- score normalized to 8
2.5/2.5Contributors — project has 9 contributing companies or organizations
0/10Dangerous-Workflow — no data
7.5/7.5Dependency-Update-Tool — update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
3.8/7.5Maintained — 4 commit(s) and 3 issue activity found in the last 90 days -- score normalized to 5
0/5Packaging — no data
0/5Pinned-Dependencies — no data
0/5SAST — SAST tool is not run on all commits -- score normalized to 0
0/5Security-Policy — security policy file not detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — no data
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated13
scorecard_versionv5.5.0
checks_inconclusive5
scorecard_aggregate5.9
Excluded from scoring (no data or not applicable): Dangerous-Workflow, Packaging, Pinned-Dependencies, Signed-Releases, 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.

45Weak · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
40/40Legible commit history — 78 of 96 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.812
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config — .php-cs-fixer.php, phpstan.neon
0/11Static type checking
0/10Reproducible environment
0/10Demonstrated agent practice — no agent-authored commits among the last 100
8/8Automated maintenance — 4 of the last 100 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependencies — no data
Inputs used
has_nixno
has_testsyes
lockfiles—
has_dockerfileno
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configyes
typecheck_configs—
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0.04
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Pinned-Dependencies. Remaining weights renormalized.
How it's scored
0/45Type-checkable code — PHP without a type-check config
55/55Manageable file sizes — 0/17 source files over 60KB
Inputs used
primary_languagePHP
largest_source_bytes17,943
source_files_sampled17
oversized_source_files0

Key facts

1,889GitHub stars
40contributors
25commits, last 12 months
3days since last push
56releases
1bus factor
14open issues
Packagistpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • No resolved dependencies carried a version and a supported ecosystem

More detail

Star and fork history 0 ★ / 312 ⇿
0Stars
312Forks
53Releases

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.

012525037530562015-122021-052026-09
Major 10Minor 4Patch 33

Each point covers 10 days.

OpenSSF Scorecard 5.9 / 10
5.9aggregate

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-09-13 06:51 UTC

10Binary-Artifactsno binaries found in the repo
3Branch-Protectionbranch protection is not maximal on development and all release branches
6CI-Tests20 out of 29 merged PRs checked by a CI test -- score normalized to 6
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
8Code-ReviewFound 23/28 approved changesets -- score normalized to 8
10Contributorsproject has 9 contributing companies or organizations
n/aDangerous-Workflowno workflows found
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
5Maintained4 commit(s) and 3 issue activity found in the last 90 days -- score normalized to 5
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
n/aSigned-Releasesno releases found
n/aToken-PermissionsNo tokens found
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 7
RegistryPackageVersion constraintManifest
Packagistpsr/http-client^1.0composer.json
Packagistpsr/http-factory^1.0composer.json
Packagistpsr/http-message^1.1|^2.0composer.json
Packagistpsr/log^2.0|^3.0composer.json
Packagistspomky-labs/base64url^2.0.4composer.json
Packagistsymfony/polyfill-php83^1.33composer.json
Packagistweb-token/jwt-library^3.4.9|^4.0.6composer.json
All dependencies 23

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

RegistryPackageVersionRelation
Packagistpsr/http-client—direct
Packagistpsr/http-factory—direct
Packagistpsr/http-message—direct
Packagistpsr/log—direct
Packagistspomky-labs/base64url—direct
Packagistsymfony/polyfill-php83—direct
Packagistweb-token/jwt-library—direct
Packagistext-curl—indirect
Packagistext-mbstring—indirect
Packagistext-openssl—indirect
Packagistfriendsofphp/php-cs-fixer—indirect
Packagistguzzlehttp/guzzle—indirect
Packagistguzzlehttp/psr7—indirect
Packagistphp—indirect
Packagistphp-http/discovery—indirect
Packagistphp-http/guzzle7-adapter—indirect
Packagistphp-http/httplug—indirect
Packagistphpstan/phpstan—indirect
Packagistphpstan/phpstan-deprecation-rules—indirect
Packagistphpstan/phpstan-phpunit—indirect
Packagistphpstan/phpstan-strict-rules—indirect
Packagistphpunit/phpunit—indirect
Packagistsymfony/polyfill-iconv—indirect
Dependency advisories not assessed

Advisory matching could not run for this report: No resolved dependencies carried a version and a supported ecosystem

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 — Packagist.