Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-08-22 12:00 UTC

stripe / stripe-php

PHP library for the Stripe API.

PHPMIT★ 4,017 stars⑂ 893 forkssince Jun 2011View on GitHub ↗

stripe/stripe-php holds a health index of 99 out of 100, placing it in the Exceptional band. It scores highest on Community & Adoption (95/100) and lowest on AI Readiness (80/100). It was last updated today. 4 contributors account for most of its recent work.

99
overall / 100
Exceptional

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.

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

Ownership

StripeOrganization
3,469 followers98 public repossince Jun 2011

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
Packagiststripe/stripe-phpv21.3.0-alpha.25,864,1026812 days agoapistripepayment-processing

Metrics by category

Vitality

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

93Exceptional · 21% of overall
How it's scored
36/36Push recencylast push 0 days ago
24.9/36Commit cadence36/52 weeks with commits
17.9/18Commit volume97 commits in the last year
10/10OpenSSF Scorecard: Maintained30 commit(s) and 4 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year97
human_commit_share0.78
days_since_last_push0
active_weeks_last_year36

Release discipline

100Exceptional
How it's scored
27/27Ships releases100 releases published
36/36Release recencylatest release 1 days ago
27/27Release cadencea release every ~3.2 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count100
latest_release_tagv21.2.1
releases_from_tagsno
days_since_latest_release1
mean_days_between_releases3.2
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?

95Exceptional · 17% of overall
How it's scored
58.5/60Stars4,017 stars
24.6/25Forks893 forks
11.3/15Watchers108 watchers
Inputs used
forks893
stars4,017
watchers108
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

92Excellent
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
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges4
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_servicesgithub.com, poser.pugx.org
has_pull_request_templateyes
How it's scored
80/80Monthly downloads5,864,102 downloads/month across packagist
18.7/20Registry dependents643 packages depend on it
Inputs used
packagesstripe/stripe-php
dependents643
ecosystemspackagist
total_downloads166,889,947
monthly_downloads5,864,102
unverified_packages_excluded

Sustainability & Governance

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

94Exceptional · 23% of overall
How it's scored
43.2/54Bus factor4 contributor(s) cover half of all commits
18.3/22.5Commit distributiontop contributor authored 19% of commits
13.5/13.5Contributor breadth99 contributors
10/10OpenSSF Scorecard: Contributorsproject has 19 contributing companies or organizations
Inputs used
bus_factor4
contributors_sampled99
top_contributor_share0.187
How it's scored
41.2/42Issue resolution98% of issues closed
25.7/30PR acceptance1,297/1,512 decided PRs merged
13/13Newcomer PR acceptance1/1 first-time contributors' PRs merged in 30d
15/15OpenSSF Scorecard: Code-Reviewall changesets reviewed
Inputs used
merged_prs1,297
open_issues12
closed_issues584
prs_merged_7d6
prs_decided_7d6
prs_merged_30d12
prs_decided_30d13
issue_closed_ratio0.98
closed_unmerged_prs215
first_time_authors_30d1
first_time_prs_merged_30d1
first_time_prs_decided_30d1
How it's scored
30/30Ownership backingorganization-owned
0/20Verified domainverified-domain status not read for this organization
25/25Owner reach3,469 followers of stripe
25/25Track record98 public repos, account ~15 yr old
Inputs used
followers3,469
owner_typeOrganization
is_verified
owner_loginstripe
public_repos98
account_age_days5,544
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 2 days ago
20/20Version history681 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesstripe/stripe-php
ecosystemspackagist
any_deprecatedno
min_days_since_publish2

Engineering Quality

Are baseline engineering and documentation practices in place?

84Excellent · 19% of overall
How it's scored
24/24CI workflows2 workflow(s)
24/24Tests present
16/16Linter config.php-cs-fixer.php
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests30 out of 30 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigyes
has_linter_configyes
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage sitehttps://stripe.com
10/10Repository description
10/10Topics2 topics
10/10Wiki
Inputs used
topicsstripe, stripe-sdk
has_wikiyes
homepagehttps://stripe.com
docs_sitehttps://stripe.com
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

81Excellent · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
6/7.5Branch-Protectionbranch protection is not maximal on development and all release branches
2.5/2.5CI-Tests30 out of 30 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
7.5/7.5Code-Reviewall changesets reviewed
2.5/2.5Contributorsproject has 19 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.5Maintained30 commit(s) and 4 issue activity found in the last 90 days -- score normalized to 10
0/5Packagingno data
0/5Pinned-Dependenciesno data
5/5SASTSAST tool is run on all commits
5/5Security-Policysecurity policy file detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsno data
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated13
scorecard_versionv5.5.0
checks_inconclusive5
scorecard_aggregate7.6
Excluded from scoring (no data or not applicable): 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 advisoriesno direct dependency carries a known advisory
0/25Indirect dependencies free of known advisoriestransitive set not separable from development and test dependencies in this scope
0/40No advisories left outstandingno advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages1
unassessed_packages6
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 1 resolved dependencies against OSV. 6 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list. 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.

80Excellent · 4% of overall
How it's scored
45/45Agent instructions.claude/CLAUDE.md
15/15Machine-readable docs (llms.txt)llms.txt served by the project website (https://stripe.com/llms.txt)
37.6/40Legible commit history55 of 78 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://stripe.com/llms.txt
legible_history_share0.705
agent_instruction_files.claude/CLAUDE.md
agent_instruction_max_bytes2,037
How it's scored
18/18One-command bootstrapMakefile, justfile
22/22Automated tests
11/11Lint / format config.php-cs-fixer.php
0/11Static type checking
0/10Reproducible environment
10/10Demonstrated agent practice5 of the last 100 commits agent-authored or agent-credited
0/8Automated maintenanceno automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependenciesno data
Inputs used
has_nixno
has_testsyes
lockfiles
has_dockerfileno
typed_languageno
bootstrap_filesMakefile, justfile
has_devcontainerno
has_linter_configyes
typecheck_configs
agent_commit_share0.05
toolchain_manifests
dependency_bot_commit_share0
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Pinned-Dependencies. Remaining weights renormalized.
How it's scored
0/45Type-checkable codePHP without a type-check config
54.9/55Manageable file sizes1/529 source files over 60KB
Inputs used
primary_languagePHP
largest_source_bytes197,717
source_files_sampled529
oversized_source_files1
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

4,017GitHub stars
99contributors
97commits, last 12 months
0days since last push
100releases
4bus factor
12open issues
Packagistpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token

More detail

Star and fork history 0 ★ / 893 ⇿
0Stars
893Forks
95Releases

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.

02004006008001,00088082011-062019-012026-08
Major 4Minor 15Patch 6

Each point covers 14 days.

OpenSSF Scorecard 7.6 / 10
7.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-08-22 12:00 UTC

10Binary-Artifactsno binaries found in the repo
8Branch-Protectionbranch protection is not maximal on development and all release branches
10CI-Tests30 out of 30 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
10Code-Reviewall changesets reviewed
10Contributorsproject has 19 contributing companies or organizations
n/aDangerous-Workflowno workflows found
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 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
10SASTSAST tool is run on all commits
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
n/aToken-PermissionsNo tokens found
10Vulnerabilities0 existing vulnerabilities detected
All dependencies 7

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

RegistryPackageVersionRelation
Packagistext-curlindirect
Packagistext-jsonindirect
Packagistext-mbstringindirect
Packagistfriendsofphp/php-cs-fixer3.94.0indirect
Packagistphpindirect
Packagistphpstan/phpstanindirect
Packagistphpunit/phpunitindirect
Dependency advisories 0

This repository publishes no package the index resolves, so its own dependency graph was assessed — 1 packages, which also include development and test pins that never ship: 0 carry known advisories, of which 0 are direct. 6 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list.

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