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

VerifiedJoseph / ntfy-php-library

PHP library for sending push notifications using ntfy

PHPMIT★ 26 stars⑂ 2 forkssince Dec 2021View on GitHub ↗

VerifiedJoseph/ntfy-php-library holds a health index of 71 out of 100, placing it in the Good band. It scores highest on Vitality (78/100) and lowest on Community & Adoption (38/100). It was last updated 11 days ago. A single contributor accounts for most of its recent work.

71
overall / 100
Good

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.

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

Ownership

JosephPersonal account
21 followers26 public repossince Jun 2016

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
Packagistverifiedjoseph/ntfy-php-libraryv4.8.22,0104611 days agopush-notificationsntfyntfy.sh

Metrics by category

Vitality

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

78Good · 21% of overall
How it's scored
28.8/36Push recency — last push 11 days ago
12.5/36Commit cadence — 18/52 weeks with commits
17.6/18Commit volume — 89 commits in the last year
10/10OpenSSF Scorecard: Maintained — 28 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year89
human_commit_share0.15
days_since_last_push11
active_weeks_last_year18
How it's scored
27/27Ships releases — 46 releases published
36/36Release recency — latest release 11 days ago
19.8/27Release cadence — a release every ~98.9 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count46
latest_release_tagv4.8.2
releases_from_tagsno
days_since_latest_release11
mean_days_between_releases98.9
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?

38Weak · 17% of overall
How it's scored
22.7/60Stars — 26 stars
0/25Forks — 2 forks
0/15Watchers — 1 watchers
Inputs used
forks2
stars26
watchers1
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonbelow_threshold
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (MIT)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges3
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicesshields.io
has_pull_request_templateno
How it's scored
44/80Monthly downloads — 2,010 downloads/month across packagist
3.2/20Registry dependents — 2 packages depend on it
Inputs used
packagesverifiedjoseph/ntfy-php-library
dependents2
ecosystemspackagist
total_downloads39,638
monthly_downloads2,010
unverified_packages_excluded—

Sustainability & Governance

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

59Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
0.5/22.5Commit distribution — top contributor authored 98% of commits
2.7/13.5Contributor breadth — 2 contributors
6/10OpenSSF Scorecard: Contributors — project has 2 contributing companies or organizations -- score normalized to 6
Inputs used
bus_factor1
contributors_sampled2
top_contributor_share0.979
How it's scored
42/42Issue resolution — 100% of issues closed
28/30PR acceptance — 557/596 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/3 approved changesets -- score normalized to 0
Inputs used
merged_prs557
open_issues0
closed_issues4
prs_merged_7d0
prs_decided_7d0
prs_merged_30d1
prs_decided_30d1
issue_closed_ratio1
closed_unmerged_prs39
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
10/30Ownership backing — personal (user) account
0/20Verified domain — not applicable to user accounts
9.7/25Owner reach — 21 followers of VerifiedJoseph
22.4/25Track record — 26 public repos, account ~10 yr old
Inputs used
followers21
owner_typeUser
is_verified—
owner_loginVerifiedJoseph
public_repos26
account_age_days3,732
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on packagist
35/35Publish recency — latest publish 11 days ago
20/20Version history — 46 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesverifiedjoseph/ntfy-php-library
ecosystemspackagist
any_deprecatedno
min_days_since_publish11

Engineering Quality

Are baseline engineering and documentation practices in place?

78Good · 19% of overall
How it's scored
24/24CI workflows — 2 workflow(s)
24/24Tests present
16/16Linter config — phpcs.xml
0/9.6Pre-commit hooks
0/6.4.editorconfig
6/20OpenSSF Scorecard: CI-Tests — 11 out of 30 merged PRs checked by a CI test -- score normalized to 3
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno

Documentation

90Excellent
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage site — https://packagist.org/packages/verifiedjoseph/ntfy-php-library
10/10Repository description
10/10Topics — 6 topics
0/10Wiki
Inputs used
topicsphp, php-library, composer-package, ntfy, notifications, push-notifications
has_wikino
homepagehttps://packagist.org/packages/verifiedjoseph/ntfy-php-library
docs_sitehttps://packagist.org/packages/verifiedjoseph/ntfy-php-library
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

65Good · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — no data
0.8/2.5CI-Tests — 11 out of 30 merged PRs checked by a CI test -- score normalized to 3
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0/7.5Code-Review — Found 0/3 approved changesets -- score normalized to 0
1.5/2.5Contributors — project has 2 contributing companies or organizations -- score normalized to 6
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
7.5/7.5Maintained — 28 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
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_evaluated12
scorecard_versionv5.5.0
checks_inconclusive6
scorecard_aggregate5.6
Excluded from scoring (no data or not applicable): Branch-Protection, Dangerous-Workflow, Packaging, Pinned-Dependencies, Signed-Releases, Token-Permissions. 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
advisories0
affected_packages0
assessed_packages38
unassessed_packages0
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 38 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.

46Weak · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
0/40Legible commit history — no 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
22/22Automated tests
11/11Lint / format config — phpcs.xml
0/11Static type checking
10/10Reproducible environment — devcontainer, Dockerfile, lockfile
0/10Demonstrated agent practice — no agent-authored commits among the last 100
8/8Automated maintenance — 85 of the last 100 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependencies — no data
Inputs used
has_nixno
has_testsyes
lockfilescomposer.lock
has_dockerfileyes
typed_languageno
bootstrap_files—
has_devcontaineryes
has_linter_configyes
typecheck_configs—
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0.85
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/30 source files over 60KB
Inputs used
primary_languagePHP
largest_source_bytes5,561
source_files_sampled30
oversized_source_files0
How it's scored
0/40API schema (OpenAPI/GraphQL/proto) — not applicable to this kind of software
0/20MCP server — not applicable to this kind of software
40/40Runnable examples — examples
Inputs used
example_dirsexamples
has_mcp_signalno
api_schema_files—
interfaces_expected_of—
Excluded from scoring (no data or not applicable): API schema (OpenAPI/GraphQL/proto), MCP server. Remaining weights renormalized.

Key facts

26GitHub stars
2contributors
89commits, last 12 months
11days since last push
46releases
1bus factor
0open issues
Packagistpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • Star history carried forward from 2026-02-06: GitHub restricted the stargazers API to repository admins, so it can no longer be collected. The repository has 26 stars today.

More detail

Star and fork history 25 ★ / 2 ⇿
25Stars
2Forks
37Releases

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.

Star history is shown as collected on 2026-02-06. GitHub restricted the stargazers API to repository administrators in July 2026, so this series can no longer be extended; the current star total above remains live.

051015202525222022-042024-032026-02
Major 2Minor 9Patch 26

Each point covers 4 days.

OpenSSF Scorecard 5.6 / 10
5.6aggregate

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-12 15:29 UTC

10Binary-Artifactsno binaries found in the repo
n/aBranch-Protectioninternal error: error during branchesHandler.setup: internal error: some github tokens can't read classic branch protection rules: https://github.com/ossf/scorecard-action/blob/main/docs/authentication/fine-grained-auth-token.md
3CI-Tests11 out of 30 merged PRs checked by a CI test -- score normalized to 3
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/3 approved changesets -- score normalized to 0
6Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
n/aDangerous-Workflowno workflows found
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained28 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
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
n/aToken-PermissionsNo tokens found
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 1
RegistryPackageVersion constraintManifest
Packagistguzzlehttp/guzzle^7.4composer.json
All dependencies 38

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

RegistryPackageVersionRelation
Packagistguzzlehttp/guzzle7.15.5direct
Packagistguzzlehttp/promises2.5.3indirect
Packagistguzzlehttp/psr72.13.1indirect
Packagistmyclabs/deep-copy1.14.0indirect
Packagistnikic/php-parser5.8.0indirect
Packagistphar-io/manifest2.0.4indirect
Packagistphar-io/version3.2.1indirect
Packagistphpstan/phpstan2.2.9indirect
Packagistphpstan/phpstan-deprecation-rules2.0.5indirect
Packagistphpstan/phpstan-phpunit2.0.18indirect
Packagistphpunit/php-code-coverage12.5.7indirect
Packagistphpunit/php-file-iterator6.0.2indirect
Packagistphpunit/php-invoker6.0.0indirect
Packagistphpunit/php-text-template5.0.0indirect
Packagistphpunit/php-timer8.0.0indirect
Packagistphpunit/phpunit12.5.33indirect
Packagistpsr/http-client1.0.3indirect
Packagistpsr/http-factory1.1.0indirect
Packagistpsr/http-message2.0indirect
Packagistralouphie/getallheaders3.0.3indirect
Packagistsebastian/cli-parser4.2.1indirect
Packagistsebastian/comparator7.1.8indirect
Packagistsebastian/complexity5.0.0indirect
Packagistsebastian/diff7.0.1indirect
Packagistsebastian/environment8.1.2indirect
Packagistsebastian/exporter7.0.3indirect
Packagistsebastian/global-state8.0.3indirect
Packagistsebastian/lines-of-code4.0.1indirect
Packagistsebastian/object-enumerator7.0.0indirect
Packagistsebastian/object-reflector5.0.0indirect
Packagistsebastian/recursion-context7.0.1indirect
Packagistsebastian/type6.0.4indirect
Packagistsebastian/version6.0.0indirect
Packagistsquizlabs/php_codesniffer4.0.4indirect
Packagiststaabm/side-effects-detector1.0.5indirect
Packagistsymfony/deprecation-contracts3.7.1indirect
Packagistsymfony/polyfill-php801.37.0indirect
Packagisttheseer/tokenizer2.0.1indirect
Dependency advisories 0

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

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