Public record
Software health reportschema 0.12.0 · metrics 2.10.0 · 2026-07-17 19:38 UTC

bitpay / php-bitpay-client-v2

PHP implementation for the BitPay Cryptographically Secure RESTful API

PHPMIT★ 42 stars⑂ 42 forkssince Sep 2019View on GitHub ↗
KindLibraryCommand-line toolhow this is determined

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

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

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

Ownership

BitPayOrganization
400 followers214 public repossince Oct 2012

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
Packagistbitpay/sdk10.1.49,2865718 days agopaymentgatewaybitcoincashbitpay

Metrics by category

Vitality

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

87Excellent · 21% of overall
How it's scored
36/36Push recencylast push 0 days ago
20.1/36Commit cadence29/52 weeks with commits
17.3/18Commit volume84 commits in the last year
10/10OpenSSF Scorecard: Maintained23 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year84
human_commit_share
days_since_last_push0
active_weeks_last_year29
How it's scored
27/27Ships releases57 releases published
36/36Release recencylatest release 18 days ago
19.8/27Release cadencea release every ~50.4 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count57
latest_release_tag10.1.4
releases_from_tagsno
days_since_latest_release18
mean_days_between_releases50.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?

50Moderate · 17% of overall
How it's scored
26.2/60Stars42 stars
13.4/25Forks42 forks
3.9/15Watchers6 watchers
Inputs used
forks42
stars42
watchers6
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
52.9/80Monthly downloads9,286 downloads/month across packagist
4.7/20Registry dependents4 packages depend on it
Inputs used
packagesbitpay/sdk
dependents4
ecosystemspackagist
total_downloads366,790
monthly_downloads9,286
unverified_packages_excluded

Sustainability & Governance

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

73Good · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
9/22.5Commit distributiontop contributor authored 60% of commits
13.5/13.5Contributor breadth20 contributors
3/10OpenSSF Scorecard: Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
Inputs used
bus_factor1
contributors_sampled20
top_contributor_share0.599
How it's scored
42/42Issue resolution100% of issues closed
21.9/30PR acceptance279/383 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
4.5/15OpenSSF Scorecard: Code-ReviewFound 3/8 approved changesets -- score normalized to 3
Inputs used
merged_prs279
open_issues0
closed_issues43
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio1
closed_unmerged_prs104
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
18.7/25Owner reach400 followers of bitpay
25/25Track record214 public repos, account ~13 yr old
Inputs used
followers400
owner_typeOrganization
is_verified
owner_loginbitpay
public_repos214
account_age_days5,024
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 18 days ago
20/20Version history57 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesbitpay/sdk
ecosystemspackagist
any_deprecatedno
min_days_since_publish18

Engineering Quality

Are baseline engineering and documentation practices in place?

67Good · 19% of overall
How it's scored
24/24CI workflows3 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests12 out of 12 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno
How it's scored
30/30README
25/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
0/10Topics
0/10Wiki
Inputs used
topics
has_wikino
homepage
docs_site
has_readmeyes
has_docs_diryes
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.5/2.5CI-Tests12 out of 12 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
2.2/7.5Code-ReviewFound 3/8 approved changesets -- score normalized to 3
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.5Maintained23 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
5.2/7.5Vulnerabilities3 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.

40Weak · 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
10/10Reproducible environmentlockfile
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
lockfilescomposer.lock
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
53.9/55Manageable file sizes3/152 source files over 60KB
Inputs used
primary_languagePHP
largest_source_bytes575,884
source_files_sampled152
oversized_source_files3
How it's scored
0/40API schema (OpenAPI/GraphQL/proto)not applicable to this kind of software
0/20MCP servernot applicable to this kind of software
40/40Runnable examplesexamples
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

42GitHub stars
20contributors
84commits, last 12 months
0days since last push
57releases
1bus factor
0open 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-17 19:38 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
10CI-Tests12 out of 12 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
3Code-ReviewFound 3/8 approved changesets -- score normalized to 3
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
10Maintained23 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
7Vulnerabilities3 existing vulnerabilities detected
Direct dependencies 5
RegistryPackageVersion constraintManifest
Packagistbitpay/key-utils^2.1composer.json
Packagistguzzlehttp/guzzle^7.9composer.json
Packagistsymfony/yaml^5.4 || ^6.4 || ^7.0composer.json
Packagistnetresearch/jsonmapper^6.0composer.json
Packagistsymfony/console^4.4 || ^5.4 || ^6.4 || ^7.3.1composer.json
All dependencies 48

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

RegistryPackageVersionRelation
Packagistbitpay/key-utils2.2.0direct
Packagistguzzlehttp/guzzle7.14.2direct
Packagistnetresearch/jsonmapper6.0.0direct
Packagistsymfony/console7.4.8direct
Packagistsymfony/yaml7.4.8direct
Packagistguzzlehttp/promises2.5.1indirect
Packagistguzzlehttp/psr72.12.5indirect
Packagistmyclabs/deep-copy1.13.4indirect
Packagistnikic/php-parser5.7.0indirect
Packagistphar-io/manifest2.0.4indirect
Packagistphar-io/version3.2.1indirect
Packagistphpunit/php-code-coverage11.0.12indirect
Packagistphpunit/php-file-iterator5.1.1indirect
Packagistphpunit/php-invoker5.0.1indirect
Packagistphpunit/php-text-template4.0.1indirect
Packagistphpunit/php-timer7.0.1indirect
Packagistphpunit/phpunit11.5.55indirect
Packagistpsr/container2.0.2indirect
Packagistpsr/http-client1.0.3indirect
Packagistpsr/http-factory1.1.0indirect
Packagistpsr/http-message2.0indirect
Packagistralouphie/getallheaders3.0.3indirect
Packagistsebastian/cli-parser3.0.2indirect
Packagistsebastian/code-unit3.0.3indirect
Packagistsebastian/code-unit-reverse-lookup4.0.1indirect
Packagistsebastian/comparator6.3.3indirect
Packagistsebastian/complexity4.0.1indirect
Packagistsebastian/diff6.0.2indirect
Packagistsebastian/environment7.2.1indirect
Packagistsebastian/exporter6.3.2indirect
Packagistsebastian/global-state7.0.2indirect
Packagistsebastian/lines-of-code3.0.1indirect
Packagistsebastian/object-enumerator6.0.1indirect
Packagistsebastian/object-reflector4.0.1indirect
Packagistsebastian/recursion-context6.0.3indirect
Packagistsebastian/type5.1.3indirect
Packagistsebastian/version5.0.2indirect
Packagistsquizlabs/php_codesniffer4.0.1indirect
Packagiststaabm/side-effects-detector1.0.5indirect
Packagistsymfony/deprecation-contracts3.7.1indirect
Packagistsymfony/polyfill-ctype1.34.0indirect
Packagistsymfony/polyfill-intl-grapheme1.34.0indirect
Packagistsymfony/polyfill-intl-normalizer1.34.0indirect
Packagistsymfony/polyfill-mbstring1.34.0indirect
Packagistsymfony/polyfill-php801.37.0indirect
Packagistsymfony/service-contracts3.6.1indirect
Packagistsymfony/string7.4.8indirect
Packagisttheseer/tokenizer1.3.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.12.0 — full methodology · metrics wiki.

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