Public record
Software health reportschema 0.15.0 · metrics 2.10.0 · 2026-07-20 04:24 UTC

php-mqtt / client

An MQTT client written in and for PHP.

PHPMIT★ 442 stars⑂ 74 forkssince Sep 2019View on GitHub ↗

php-mqtt/client holds a health index of 69 out of 100, placing it in the Good band. It scores highest on Vitality (72/100) and lowest on AI Readiness (24/100). It was last updated today. A single contributor accounts for most of its recent work.

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

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

Ownership

php-mqttOrganization
21 followers3 public repossince Sep 2019

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
Packagistphp-mqtt/clientv2.3.2126,62130113 days agoclientpublishsubscribemqtt

Metrics by category

Vitality

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

72Good · 21% of overall
How it's scored
36/36Push recencylast push 0 days ago
11.8/36Commit cadence17/52 weeks with commits
13/18Commit volume27 commits in the last year
10/10OpenSSF Scorecard: Maintained14 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year27
human_commit_share
days_since_last_push0
active_weeks_last_year17
How it's scored
27/27Ships releases29 releases published
27/36Release recencylatest release 113 days ago
12.6/27Release cadencea release every ~133.9 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count29
latest_release_tagv2.3.2
releases_from_tagsno
days_since_latest_release113
mean_days_between_releases133.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?

63Moderate · 17% of overall
How it's scored
42.9/60Stars442 stars
15.5/25Forks74 forks
6.8/15Watchers18 watchers
Inputs used
forks74
stars442
watchers18
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized 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_badges
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services
has_pull_request_templateno
How it's scored
68/80Monthly downloads126,621 downloads/month across packagist
10.8/20Registry dependents41 packages depend on it
Inputs used
packagesphp-mqtt/client
dependents41
ecosystemspackagist
total_downloads2,517,512
monthly_downloads126,621
unverified_packages_excluded

Sustainability & Governance

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

67Good · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
8.5/22.5Commit distributiontop contributor authored 62% of commits
13.5/13.5Contributor breadth14 contributors
3/10OpenSSF Scorecard: Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
Inputs used
bus_factor1
contributors_sampled14
top_contributor_share0.622
How it's scored
40.7/42Issue resolution97% of issues closed
24.6/30PR acceptance109/133 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
1.5/15OpenSSF Scorecard: Code-ReviewFound 2/12 approved changesets -- score normalized to 1
Inputs used
merged_prs109
open_issues3
closed_issues94
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio0.969
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
30/30Ownership backingorganization-owned
0/20Verified domainverified-domain status not read for this organization
9.7/25Owner reach21 followers of php-mqtt
16.4/25Track record3 public repos, account ~6 yr old
Inputs used
followers21
owner_typeOrganization
is_verified
owner_loginphp-mqtt
public_repos3
account_age_days2,500
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 113 days ago
20/20Version history30 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesphp-mqtt/client
ecosystemspackagist
any_deprecatedno
min_days_since_publish113

Engineering Quality

Are baseline engineering and documentation practices in place?

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

Documentation

50Moderate
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics5 topics
0/10Wiki
Inputs used
topicsphp, mqtt, mqtt-client, mqtt-library, php-mqtt
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?

54Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionno data
2.2/2.5CI-Tests21 out of 22 merged PRs checked by a CI test -- score normalized to 9
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0.8/7.5Code-ReviewFound 2/12 approved changesets -- score normalized to 1
0.8/2.5Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
10/10Dangerous-Workflowno dangerous workflow patterns detected
7.5/7.5Dependency-Update-Toolupdate tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
7.5/7.5Maintained14 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
0/5Packagingno data
0/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0/5SASTSAST tool is not run on all commits -- score normalized to 0
0/5Security-Policysecurity policy file not detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate5.4
Excluded from scoring (no data or not applicable): Branch-Protection, Packaging, Signed-Releases. 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.

24At Risk · 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
22/22Automated tests
0/11Lint / format config
0/11Static type checking
0/10Reproducible environment
0/10Demonstrated agent practiceno data
5/8Automated maintenancedependency automation configured, none observed in the sampled commits
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfiles
has_dockerfileno
typed_languageno
bootstrap_files
has_devcontainerno
has_linter_configno
typecheck_configs
agent_commit_share
toolchain_manifests
dependency_bot_commit_share0
Excluded from scoring (no data or not applicable): Demonstrated agent practice. Remaining weights renormalized.
How it's scored
0/45Type-checkable codePHP without a type-check config
55/55Manageable file sizes0/48 source files over 60KB
Inputs used
primary_languagePHP
largest_source_bytes50,658
source_files_sampled48
oversized_source_files0

Key facts

442GitHub stars
14contributors
27commits, last 12 months
0days since last push
29releases
1bus factor
3open issues
Packagistpackage ecosystems

More detail

OpenSSF Scorecard 5.4 / 10
5.4aggregate

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-20 04:23 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
9CI-Tests21 out of 22 merged PRs checked by a CI test -- score normalized to 9
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
1Code-ReviewFound 2/12 approved changesets -- score normalized to 1
3Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained14 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 2
RegistryPackageVersion constraintManifest
Packagistpsr/log^1.1|^2.0|^3.0composer.json
Packagistmyclabs/php-enum^1.7composer.json
All dependencies 32

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

RegistryPackageVersionRelation
Packagistpsr/log1.1.0direct
Packagistdoctrine/instantiator1.3.1indirect
Packagistmyclabs/deep-copy1.10.1indirect
Packagistphar-io/manifest1.0.3indirect
Packagistphar-io/version2.0.1indirect
Packagistphpdocumentor/reflection-common2.2.0indirect
Packagistphpdocumentor/reflection-docblock5.2.0indirect
Packagistphpdocumentor/type-resolver1.3.0indirect
Packagistphpspec/prophecy1.11.1indirect
Packagistphpunit/php-code-coverage7.0.10indirect
Packagistphpunit/php-file-iterator2.0.2indirect
Packagistphpunit/php-invoker3.0.2indirect
Packagistphpunit/php-text-template1.2.1indirect
Packagistphpunit/php-timer2.1.2indirect
Packagistphpunit/php-token-stream3.1.1indirect
Packagistphpunit/phpunit8.5.8indirect
Packagistsebastian/code-unit-reverse-lookup1.0.1indirect
Packagistsebastian/comparator3.0.2indirect
Packagistsebastian/diff3.0.2indirect
Packagistsebastian/environment4.2.3indirect
Packagistsebastian/exporter3.1.2indirect
Packagistsebastian/global-state3.0.0indirect
Packagistsebastian/object-enumerator3.0.3indirect
Packagistsebastian/object-reflector1.1.1indirect
Packagistsebastian/recursion-context3.0.0indirect
Packagistsebastian/resource-operations2.0.1indirect
Packagistsebastian/type1.1.3indirect
Packagistsebastian/version2.0.1indirect
Packagistsquizlabs/php_codesniffer3.5.5indirect
Packagistsymfony/polyfill-ctype1.18.0indirect
Packagisttheseer/tokenizer1.2.0indirect
Packagistwebmozart/assert1.9.1indirect
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.