Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-14 02:55 UTC

sumup / sumup-php

PHP SDK for the SumUp API.

PHP · GoApache-2.0★ 9 stars⑂ 2 forkssince Jan 2026View on GitHub ↗
KindLibraryCommand-line toolhow this is determined

sumup/sumup-php holds a health index of 86 out of 100, placing it in the Excellent band. It scores highest on Vitality (93/100) and lowest on Community & Adoption (40/100). It was last updated 1 day ago. A single contributor accounts for most of its recent work.

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

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

Ownership

SumUpOrganization · verified domain
363 followers127 public repossince Nov 2011

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
Packagistsumup/sumup-php0.1.61,583824 days agocheckoutpaymentssdksumup
Gogithub.com/sumup/sumup-phpv0.1.6-824 days ago—

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 recency — last push 1 days ago
23.5/36Commit cadence — 34/52 weeks with commits
18/18Commit volume — 185 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year185
human_commit_share0.44
days_since_last_push1
active_weeks_last_year34

Release discipline

100Exceptional
How it's scored
27/27Ships releases — 8 releases published
36/36Release recency — latest release 24 days ago
27/27Release cadence — a release every ~28.6 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count8
latest_release_tagv0.1.6
releases_from_tagsno
days_since_latest_release24
mean_days_between_releases28.6
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?

40Weak · 17% of overall
How it's scored
14.6/60Stars — 9 stars
0/25Forks — 2 forks
0/15Watchers — 0 watchers
Inputs used
forks2
stars9
watchers0
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (Apache-2.0)
0/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges5
has_contributingno
has_issue_templateno
has_code_of_conductyes
readme_badge_servicesposer.pugx.org, shields.io
has_pull_request_templateno
How it's scored
42.7/80Monthly downloads — 1,583 downloads/month across go, packagist
2/20Registry dependents — 1 packages depend on it
Inputs used
packagessumup/sumup-php, github.com/sumup/sumup-php
dependents1
ecosystemsgo, packagist
total_downloads8,909
monthly_downloads1,583
unverified_packages_excluded—

Sustainability & Governance

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

71Good · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
5/22.5Commit distribution — top contributor authored 78% of commits
2.7/13.5Contributor breadth — 2 contributors
3/10OpenSSF Scorecard: Contributors — project has 1 contributing companies or organizations -- score normalized to 3
Inputs used
bus_factor1
contributors_sampled2
top_contributor_share0.778
How it's scored
42/42Issue resolution — 100% of issues closed
27.1/30PR acceptance — 102/113 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
6/15OpenSSF Scorecard: Code-Review — Found 5/12 approved changesets -- score normalized to 4
Inputs used
merged_prs102
open_issues0
closed_issues2
prs_merged_7d1
prs_decided_7d1
prs_merged_30d3
prs_decided_30d3
issue_closed_ratio1
closed_unmerged_prs11
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
30/30Ownership backing — organization-owned
20/20Verified domain
18.4/25Owner reach — 363 followers of sumup
25/25Track record — 127 public repos, account ~14 yr old
Inputs used
followers363
owner_typeOrganization
is_verifiedyes
owner_loginsumup
public_repos127
account_age_days5,417

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 2 package(s) on go, packagist
35/35Publish recency — latest publish 24 days ago
20/20Version history — 8 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagessumup/sumup-php, github.com/sumup/sumup-php
ecosystemsgo, packagist
any_deprecatedno
min_days_since_publish24

Engineering Quality

Are baseline engineering and documentation practices in place?

76Good · 19% of overall
How it's scored
24/24CI workflows — 5 workflow(s)
24/24Tests present
16/16Linter config — .golangci.yml, .php-cs-fixer.php, phpstan.neon
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 25 out of 25 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage site — https://developer.sumup.com
10/10Repository description
10/10Topics — 4 topics
0/10Wiki
Inputs used
topicspayments, php, sdk, sumup
has_wikino
homepagehttps://developer.sumup.com
docs_sitehttps://developer.sumup.com
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

73Good · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — branch protection not enabled on development/release branches
2.5/2.5CI-Tests — 25 out of 25 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
3/7.5Code-Review — Found 5/12 approved changesets -- score normalized to 4
0.8/2.5Contributors — project has 1 contributing companies or organizations -- score normalized to 3
10/10Dangerous-Workflow — no dangerous workflow patterns detected
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 — 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
0/5Packaging — no data
5/5Pinned-Dependencies — all dependencies are pinned
5/5SAST — SAST tool is run on all commits
2/5Security-Policy — security policy file detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate6.6
Excluded from scoring (no data or not applicable): Packaging, Signed-Releases. 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_packages14
unassessed_packages5
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 14 resolved dependencies against OSV. 5 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.

71Good · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
15/15Machine-readable docs (llms.txt) — llms.txt served by the project website (https://developer.sumup.com/llms.txt)
40/40Legible commit history — 44 of 44 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://developer.sumup.com/llms.txt
legible_history_share1
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
18/18One-command bootstrap — codegen/Makefile, justfile
22/22Automated tests
11/11Lint / format config — .golangci.yml, .php-cs-fixer.php, phpstan.neon
0/11Static type checking
10/10Reproducible environment — lockfile
0/10Demonstrated agent practice — no agent-authored commits among the last 100
8/8Automated maintenance — 49 of the last 100 commits are automated dependency updates
10/10OpenSSF Scorecard: Pinned-Dependencies — all dependencies are pinned
Inputs used
has_nixno
has_testsyes
lockfilesgo.sum
has_dockerfileno
typed_languageno
bootstrap_filescodegen/Makefile, justfile
has_devcontainerno
has_linter_configyes
typecheck_configs—
agent_commit_share0
toolchain_manifestscodegen/go.mod
dependency_bot_commit_share0.49
How it's scored
0/45Type-checkable code — PHP without a type-check config
55/55Manageable file sizes — 0/208 source files over 60KB
Inputs used
primary_languagePHP
largest_source_bytes24,608
source_files_sampled208
oversized_source_files0
How it's scored
40/40API schema (OpenAPI/GraphQL/proto) — openapi.json
0/20MCP server — not applicable to this kind of software
40/40Runnable examples — examples
Inputs used
example_dirsexamples
has_mcp_signalno
api_schema_filesopenapi.json
interfaces_expected_of—
Excluded from scoring (no data or not applicable): MCP server. Remaining weights renormalized.

Key facts

9GitHub stars
2contributors
185commits, last 12 months
1days since last push
8releases
1bus factor
0open issues
Go, 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 ★ / 2 ⇿
0Stars
2Forks
5Releases

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.

111222212026-022026-042026-06
Major 0Minor 1Patch 4
OpenSSF Scorecard 6.6 / 10
6.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-14 02:55 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
10CI-Tests25 out of 25 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
4Code-ReviewFound 5/12 approved changesets -- score normalized to 4
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
10Maintained30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
10Pinned-Dependenciesall dependencies are pinned
10SASTSAST tool is run on all commits
4Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 5
RegistryPackageVersion constraintManifest
Gogithub.com/iancoleman/strcasev0.3.0codegen/go.mod
Gogithub.com/lmittmann/tintv1.2.0codegen/go.mod
Gogithub.com/pb33f/libopenapiv0.38.7codegen/go.mod
Gogithub.com/urfave/cli/v2v2.27.7codegen/go.mod
Gogo.yaml.in/yaml/v4v4.0.0-rc.6codegen/go.mod
All dependencies 19

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

RegistryPackageVersionRelation
Gogithub.com/iancoleman/strcasev0.3.0direct
Gogithub.com/lmittmann/tintv1.2.0direct
Gogithub.com/pb33f/libopenapiv0.38.7direct
Gogithub.com/urfave/cli/v2v2.27.7direct
Gogo.yaml.in/yaml/v4v4.0.0-rc.6direct
Gogithub.com/bahlo/generic-list-gov0.2.0indirect
Gogithub.com/buger/jsonparserv1.1.2indirect
Gogithub.com/cpuguy83/go-md2man/v2v2.0.7indirect
Gogithub.com/pb33f/jsonpathv0.8.2indirect
Gogithub.com/pb33f/ordered-map/v2v2.3.1indirect
Gogithub.com/russross/blackfriday/v2v2.1.0indirect
Gogithub.com/xrash/smetricsv0.0.0-20250705151800-55b8f293f342indirect
Gogolang.org/x/syncv0.22.0indirect
Packagistext-curl—indirect
Packagistfriendsofphp/php-cs-fixer3.95.24indirect
Packagistleague/oauth2-client—indirect
Packagistphp—indirect
Packagistphpstan/phpstan—indirect
Packagistphpunit/phpunit—indirect
Dependency advisories 0

This repository publishes no package the index resolves, so its own dependency graph was assessed — 14 packages, which also include development and test pins that never ship: 0 carry known advisories, of which 0 are direct. 5 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 statistics — Packagist, Go.