Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-11-19 08:23 UTC

tpay-com / tpay-openapi-php

PHPMIT★ 9 stars⑂ 16 forkssince Aug 2019View on GitHub ↗

tpay-com/tpay-openapi-php holds a health index of 73 out of 100, placing it in the Good band. It scores highest on Sustainability & Governance (80/100) and lowest on Community & Adoption (45/100). It was last updated 5 days ago. 3 contributors account for most of its recent work.

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

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

Ownership

TpayOrganization
8 followers18 public repossince Aug 2015

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
Packagisttpay-com/tpay-openapi-php2.6.022,091515 days ago

Metrics by category

Vitality

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

75Good · 21% of overall
How it's scored
36/36Push recency — last push 5 days ago
10.4/36Commit cadence — 15/52 weeks with commits
13.4/18Commit volume — 30 commits in the last year
5/10OpenSSF Scorecard: Maintained — 6 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 5
Inputs used
commits_last_year30
human_commit_share1
days_since_last_push5
active_weeks_last_year15
How it's scored
27/27Ships releases — 51 releases published
36/36Release recency — latest release 5 days ago
27/27Release cadence — a release every ~25.8 days
0/10OpenSSF Scorecard: Signed-Releases — Project has not signed or included provenance with any releases.
Inputs used
releases_count51
latest_release_tag2.6.0
releases_from_tagsno
days_since_latest_release5
mean_days_between_releases25.8

Community & Adoption

Does the project have users, downloads, attention, and a welcoming setup for contributors?

45Weak · 17% of overall
How it's scored
14.6/60Stars — 9 stars
9.8/25Forks — 16 forks
3.3/15Watchers — 5 watchers
Inputs used
forks16
stars9
watchers5
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
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_badges4
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicesgithub.com, shields.io
has_pull_request_templateno
How it's scored
57.9/80Monthly downloads — 22,091 downloads/month across packagist
6.4/20Registry dependents — 8 packages depend on it
Inputs used
packagestpay-com/tpay-openapi-php
dependents8
ecosystemspackagist
total_downloads315,946
monthly_downloads22,091
unverified_packages_excluded—

Sustainability & Governance

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

80Excellent · 23% of overall
How it's scored
36/54Bus factor — 3 contributor(s) cover half of all commits
17.3/22.5Commit distribution — top contributor authored 23% of commits
13.5/13.5Contributor breadth — 13 contributors
10/10OpenSSF Scorecard: Contributors — project has 4 contributing companies or organizations
Inputs used
bus_factor3
contributors_sampled13
top_contributor_share0.231
How it's scored
42/42Issue resolution — 100% of issues closed
28.2/30PR acceptance — 96/102 decided PRs merged
13/13Newcomer PR acceptance — 1/1 first-time contributors' PRs merged in 30d
7.5/15OpenSSF Scorecard: Code-Review — Found 16/30 approved changesets -- score normalized to 5
Inputs used
merged_prs96
open_issues0
closed_issues19
prs_merged_7d3
prs_decided_7d3
prs_merged_30d4
prs_decided_30d4
issue_closed_ratio1
closed_unmerged_prs6
first_time_authors_30d1
first_time_prs_merged_30d1
first_time_prs_decided_30d1
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain
6.9/25Owner reach — 8 followers of tpay-com
21.3/25Track record — 18 public repos, account ~11 yr old
Inputs used
followers8
owner_typeOrganization
is_verifiedno
owner_logintpay-com
public_repos18
account_age_days4,101

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on packagist
35/35Publish recency — latest publish 5 days ago
20/20Version history — 51 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagestpay-com/tpay-openapi-php
ecosystemspackagist
any_deprecatedno
min_days_since_publish5

Engineering Quality

Are baseline engineering and documentation practices in place?

65Good · 19% of overall
How it's scored
24/24CI workflows — 4 workflow(s)
24/24Tests present
16/16Linter config — .php-cs-fixer.php, phpstan.neon
0/9.6Pre-commit hooks
0/6.4.editorconfig
18/20OpenSSF Scorecard: CI-Tests — 23 out of 25 merged PRs checked by a CI test -- score normalized to 9
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
0/10Repository description
0/10Topics
10/10Wiki
Inputs used
topics—
has_wikiyes
homepage—
docs_site—
has_readmeyes
has_docs_dirno
has_descriptionno

Security

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

50Moderate · 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.2/2.5CI-Tests — 23 out of 25 merged PRs checked by a CI test -- score normalized to 9
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
3.8/7.5Code-Review — Found 16/30 approved changesets -- score normalized to 5
2.5/2.5Contributors — project has 4 contributing companies or organizations
0/10Dangerous-Workflow — no data
0/7.5Dependency-Update-Tool — no update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
3.8/7.5Maintained — 6 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 5
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 — Project has not signed or included provenance with any releases.
0/7.5Token-Permissions — no data
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated14
scorecard_versionv5.5.0
checks_inconclusive4
scorecard_aggregate3.8
Excluded from scoring (no data or not applicable): Dangerous-Workflow, Packaging, Pinned-Dependencies, 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_packages44
unassessed_packages12
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 44 resolved dependencies against OSV. 12 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.

54Moderate · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
40/40Legible commit history — 85 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.85
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config — .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
0/8Automated maintenance — no automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependencies — no data
Inputs used
has_nixno
has_testsyes
lockfilescomposer.lock
has_dockerfileno
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configyes
typecheck_configs—
agent_commit_share0
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 code — PHP without a type-check config
54.8/55Manageable file sizes — 1/338 source files over 60KB
Inputs used
primary_languagePHP
largest_source_bytes133,867
source_files_sampled338
oversized_source_files1
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

9GitHub stars
13contributors
30commits, last 12 months
5days since last push
51releases
3bus factor
0open 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 ★ / 16 ⇿
0Stars
16Forks
46Releases

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.

04812161612021-022023-122026-10
Major 1Minor 13Patch 32

Each point covers 6 days.

OpenSSF Scorecard 3.8 / 10
3.8aggregate

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-11-19 08:23 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
9CI-Tests23 out of 25 merged PRs checked by a CI test -- score normalized to 9
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
5Code-ReviewFound 16/30 approved changesets -- score normalized to 5
10Contributorsproject has 4 contributing companies or organizations
n/aDangerous-Workflowno workflows found
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
5Maintained6 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 5
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
0Signed-ReleasesProject has not signed or included provenance with any releases.
n/aToken-PermissionsNo tokens found
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 8
RegistryPackageVersion constraintManifest
Packagistergebnis/composer-normalize^2.35.dev-tools/composer.json
Packagistkubawerlos/composer-smaller-lock^1.0.1.dev-tools/composer.json
Packagistkubawerlos/php-cs-fixer-custom-fixers^3.16.2.dev-tools/composer.json
Packagisttpay-com/coding-standards^1.0.1.dev-tools/composer.json
Packagistvimeo/psalm^5.15.0.dev-tools/composer.json
Packagistpsr/cache^1 || ^2 || ^3composer.json
Packagistpsr/log^1 || ^2 || ^3composer.json
Packagistpsr/simple-cache^1 || ^2 || ^3composer.json
All dependencies 56

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

RegistryPackageVersionRelation
Packagistergebnis/composer-normalize2.35.0direct
Packagistkubawerlos/composer-smaller-lock1.0.1direct
Packagistkubawerlos/php-cs-fixer-custom-fixers3.16.2direct
Packagistpsr/cache—direct
Packagistpsr/log—direct
Packagistpsr/log3.0.0direct
Packagistpsr/simple-cache—direct
Packagisttpay-com/coding-standards1.0.1direct
Packagistvimeo/psalm5.15.0direct
Packagistamphp/amp2.6.2indirect
Packagistamphp/byte-stream1.8.1indirect
Packagistcomposer/pcre3.1.0indirect
Packagistcomposer/semver3.3.2indirect
Packagistcomposer/xdebug-handler3.0.3indirect
Packagistdnoegel/php-xdg-base-dir0.1.1indirect
Packagistdoctrine/deprecations1.1.1indirect
Packagistergebnis/json1.0.1indirect
Packagistergebnis/json-normalizer4.2.0indirect
Packagistergebnis/json-pointer3.2.0indirect
Packagistergebnis/json-printer3.3.0indirect
Packagistergebnis/json-schema-validator4.0.0indirect
Packagistext-curl—indirect
Packagistext-fileinfo—indirect
Packagistext-json—indirect
Packagistext-openssl—indirect
Packagistfelixfbecker/advanced-json-rpc3.2.1indirect
Packagistfelixfbecker/language-server-protocol1.5.2indirect
Packagistfidry/cpu-core-counter0.5.1indirect
Packagistjustinrainbow/json-schema5.2.12indirect
Packagistlocalheinz/diff1.1.1indirect
Packagistnetresearch/jsonmapper4.2.0indirect
Packagistnikic/php-parser4.17.1indirect
Packagistphp—indirect
Packagistphp-cs-fixer/shim3.23.0indirect
Packagistphp-parallel-lint/php-parallel-lint—indirect
Packagistphpdocumentor/reflection-common2.2.0indirect
Packagistphpdocumentor/reflection-docblock5.3.0indirect
Packagistphpdocumentor/type-resolver1.7.3indirect
Packagistphpseclib/phpseclib—indirect
Packagistphpstan/phpdoc-parser1.23.1indirect
Packagistphpstan/phpstan1.10.32indirect
Packagistphpunit/phpunit—indirect
Packagistpsr/container2.0.2indirect
Packagistpsx/cache—indirect
Packagistsebastian/diff5.0.3indirect
Packagistspatie/array-to-xml3.2.0indirect
Packagistsymfony/console6.3.4indirect
Packagistsymfony/deprecation-contracts3.3.0indirect
Packagistsymfony/filesystem6.3.1indirect
Packagistsymfony/polyfill-ctype1.28.0indirect
Packagistsymfony/polyfill-intl-grapheme1.28.0indirect
Packagistsymfony/polyfill-intl-normalizer1.28.0indirect
Packagistsymfony/polyfill-mbstring1.28.0indirect
Packagistsymfony/service-contracts3.3.0indirect
Packagistsymfony/string6.3.2indirect
Packagistwebmozart/assert1.11.0indirect
Dependency advisories 0

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