Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-12 21:16 UTC

wl-online-payments-direct / sdk-php

PHPCustom license★ 7 stars⑂ 6 forkssince Feb 2020View on GitHub ↗

wl-online-payments-direct/sdk-php holds a health index of 54 out of 100, placing it in the Moderate band. It scores highest on Vitality (74/100) and lowest on AI Readiness (27/100). It was last updated 18 days ago. A single contributor accounts for most of its recent work.

54
overall / 100
Moderate

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.

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

Ownership

25 followers45 public repossince Jan 2013

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
Packagistwl-online-payments-direct/sdk-php10.0.031,3267518 days agosdk

Metrics by category

Vitality

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

74Good · 21% of overall
How it's scored
28.8/36Push recency — last push 18 days ago
11.8/36Commit cadence — 17/52 weeks with commits
12.4/18Commit volume — 23 commits in the last year
4/10OpenSSF Scorecard: Maintained — 5 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 4
Inputs used
commits_last_year23
human_commit_share1
days_since_last_push18
active_weeks_last_year17

Release discipline

100Exceptional
How it's scored
27/27Ships releases — 75 releases published
36/36Release recency — latest release 18 days ago
27/27Release cadence — a release every ~18.8 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count75
latest_release_tag10.0.0
releases_from_tagsno
days_since_latest_release18
mean_days_between_releases18.8
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?

41Weak · 17% of overall
How it's scored
12.6/60Stars — 7 stars
5.8/25Forks — 6 forks
5/15Watchers — 9 watchers
Inputs used
forks6
stars7
watchers9
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonbelow_threshold
How it's scored
22.5/22.5README
16.9/22.5License — license file present, not a recognized license
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges0
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services—
has_pull_request_templateno
How it's scored
59.9/80Monthly downloads — 31,326 downloads/month across packagist
4/20Registry dependents — 3 packages depend on it
Inputs used
packageswl-online-payments-direct/sdk-php
dependents3
ecosystemspackagist
total_downloads851,218
monthly_downloads31,326
unverified_packages_excluded—

Sustainability & Governance

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

54Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
3.9/22.5Commit distribution — top contributor authored 82% 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.825
How it's scored
42/42Issue resolution — 100% of issues closed
0/30PR acceptance — 0/3 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/30 approved changesets -- score normalized to 0
Inputs used
merged_prs0
open_issues0
closed_issues22
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio1
closed_unmerged_prs3
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
0/20Verified domain
10.2/25Owner reach — 25 followers of wl-online-payments-direct
24.1/25Track record — 45 public repos, account ~13 yr old
Inputs used
followers25
owner_typeOrganization
is_verifiedno
owner_loginwl-online-payments-direct
public_repos45
account_age_days5,002

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on packagist
35/35Publish recency — latest publish 18 days ago
20/20Version history — 75 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packageswl-online-payments-direct/sdk-php
ecosystemspackagist
any_deprecatedno
min_days_since_publish18

Engineering Quality

Are baseline engineering and documentation practices in place?

51Moderate · 19% of overall
How it's scored
0/24CI workflows
24/24Tests present
16/16Linter config — phpstan.neon
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests — no data
Inputs used
has_cino
has_testsyes
has_editorconfigyes
has_linter_configyes
has_precommit_configno
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: CI-Tests. Remaining weights renormalized.
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?

45Weak · 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
0/2.5CI-Tests — no data
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0/7.5Code-Review — Found 0/30 approved changesets -- score normalized to 0
0.8/2.5Contributors — project has 1 contributing companies or organizations -- score normalized to 3
0/10Dangerous-Workflow — no data
0/7.5Dependency-Update-Tool — no update tool detected
0/5Fuzzing — project is not fuzzed
2.2/2.5License — license file detected
3/7.5Maintained — 5 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 4
0/5Packaging — no data
0/5Pinned-Dependencies — no data
0/5SAST — no SAST tool detected
0/5Security-Policy — security policy file not detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — no data
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated12
scorecard_versionv5.5.0
checks_inconclusive6
scorecard_aggregate3.1
Excluded from scoring (no data or not applicable): CI-Tests, 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 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_packages2
unassessed_packages8
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 2 resolved dependencies against OSV. 8 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.

27At Risk · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
0/40Legible commit history — 0 of 80 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config — phpstan.neon
0/11Static type checking
0/10Reproducible environment
0/10Demonstrated agent practice — no agent-authored commits among the last 80
0/8Automated maintenance — no automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependencies — no data
Inputs used
has_nixno
has_testsyes
lockfiles—
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
55/55Manageable file sizes — 0/609 source files over 60KB
Inputs used
primary_languagePHP
largest_source_bytes35,655
source_files_sampled609
oversized_source_files0

Key facts

7GitHub stars
2contributors
23commits, last 12 months
18days since last push
75releases
1bus factor
0open issues
Packagistpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • Star history carried forward from 2025-12-09: GitHub restricted the stargazers API to repository admins, so it can no longer be collected. The repository has 7 stars today.

More detail

Star and fork history 7 ★ / 6 ⇿
7Stars
6Forks
44Releases

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.

Star history is shown as collected on 2025-12-09. GitHub restricted the stargazers API to repository administrators in July 2026, so this series can no longer be extended; the current star total above remains live.

01234566612022-032024-012025-12
Major 4Minor 35Patch 5

Each point covers 4 days.

OpenSSF Scorecard 3.1 / 10
3.1aggregate

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-12 21:16 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
n/aCI-Testsno pull request found
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/30 approved changesets -- score normalized to 0
3Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
n/aDangerous-Workflowno workflows found
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
9Licenselicense file detected
4Maintained5 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 4
n/aPackagingpackaging workflow not detected
n/aPinned-Dependenciesno dependencies found
0SASTno SAST tool detected
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
n/aToken-PermissionsNo tokens found
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 1
RegistryPackageVersion constraintManifest
Packagistrobtimus/multipart~1.0composer.json
All dependencies 10

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

RegistryPackageVersionRelation
Packagistrobtimus/multipart—direct
Packagistdoctrine/instantiator1.5.0indirect
Packagistext-curl—indirect
Packagistext-json—indirect
Packagistext-mbstring—indirect
Packagistext-zlib—indirect
Packagistphp—indirect
Packagistphpstan/phpstan2.1.32indirect
Packagistphpunit/phpunit—indirect
Packagistsquizlabs/php_codesniffer—indirect
Dependency advisories 0

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