Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-05 15:16 UTC

Sylius / PayPalPlugin

Official integration with PayPal Commerce Platform

PHPMIT★ 46 stars⑂ 67 forkssince Jun 2020View on GitHub ↗

Sylius/PayPalPlugin holds a health index of 81 out of 100, placing it in the Excellent band. It scores highest on Vitality (86/100) and lowest on AI Readiness (35/100). It was last updated today. 2 contributors account for most of its recent work.

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

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

Ownership

Sylius eCommerceOrganization · verified domain
199 followers165 public repossince Apr 2011

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
Packagistsylius/paypal-pluginv2.0.1141,3146046 days agosyliussylius-plugin

Metrics by category

Vitality

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

86Excellent · 21% of overall
How it's scored
36/36Push recencylast push 0 days ago
11.8/36Commit cadence17/52 weeks with commits
18/18Commit volume101 commits in the last year
10/10OpenSSF Scorecard: Maintained20 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year101
human_commit_share1
days_since_last_push0
active_weeks_last_year17

Release discipline

100Exceptional
How it's scored
27/27Ships releases60 releases published
36/36Release recencylatest release 46 days ago
27/27Release cadencea release every ~21.6 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count60
latest_release_tagv2.0.11
releases_from_tagsno
days_since_latest_release46
mean_days_between_releases21.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?

63Moderate · 17% of overall
How it's scored
26.8/60Stars46 stars
15.2/25Forks67 forks
6/15Watchers13 watchers
Inputs used
forks67
stars46
watchers13
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (MIT)
18/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges0
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_services
has_pull_request_templateyes
How it's scored
61.5/80Monthly downloads41,314 downloads/month across packagist
5.2/20Registry dependents5 packages depend on it
Inputs used
packagessylius/paypal-plugin
dependents5
ecosystemspackagist
total_downloads1,597,225
monthly_downloads41,314
unverified_packages_excluded

Sustainability & Governance

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

77Good · 23% of overall
How it's scored
25.2/54Bus factor2 contributor(s) cover half of all commits
15.3/22.5Commit distributiontop contributor authored 32% of commits
13.5/13.5Contributor breadth32 contributors
10/10OpenSSF Scorecard: Contributorsproject has 11 contributing companies or organizations
Inputs used
bus_factor2
contributors_sampled32
top_contributor_share0.32
How it's scored
33.7/42Issue resolution80% of issues closed
16.4/30PR acceptance319/583 decided PRs merged
0/13Newcomer PR acceptance0/1 first-time contributors' PRs merged in 30d
10.5/15OpenSSF Scorecard: Code-ReviewFound 10/14 approved changesets -- score normalized to 7
Inputs used
merged_prs319
open_issues17
closed_issues69
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d1
issue_closed_ratio0.802
closed_unmerged_prs264
first_time_authors_30d1
first_time_prs_merged_30d0
first_time_prs_decided_30d1
How it's scored
30/30Ownership backingorganization-owned
20/20Verified domain
16.5/25Owner reach199 followers of Sylius
25/25Track record165 public repos, account ~15 yr old
Inputs used
followers199
owner_typeOrganization
is_verifiedyes
owner_loginSylius
public_repos165
account_age_days5,627

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable1 package(s) on packagist
35/35Publish recencylatest publish 46 days ago
20/20Version history60 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagessylius/paypal-plugin
ecosystemspackagist
any_deprecatedno
min_days_since_publish46

Engineering Quality

Are baseline engineering and documentation practices in place?

58Moderate · 19% of overall
How it's scored
24/24CI workflows2 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
16/20OpenSSF Scorecard: CI-Tests12 out of 14 merged PRs checked by a CI test -- score normalized to 8
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno

Documentation

50Moderate
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics6 topics
0/10Wiki
Inputs used
topicspaypal, sylius, ecommerce, hacktoberfest, payment-gateway, payment
has_wikino
homepage
docs_site
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

63Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionno data
2/2.5CI-Tests12 out of 14 merged PRs checked by a CI test -- score normalized to 8
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
5.2/7.5Code-ReviewFound 10/14 approved changesets -- score normalized to 7
2.5/2.5Contributorsproject has 11 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.5Maintained20 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 10
0/5Packagingno data
0/5Pinned-Dependenciesno data
0/5SASTSAST tool is not run on all commits -- score normalized to 0
4.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_evaluated12
scorecard_versionv5.5.0
checks_inconclusive6
scorecard_aggregate6.3
Excluded from scoring (no data or not applicable): Branch-Protection, Dangerous-Workflow, Packaging, Pinned-Dependencies, Signed-Releases, Token-Permissions. 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.

35Weak · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
28.3/40Legible commit history53 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.53
agent_instruction_files
agent_instruction_max_bytes
How it's scored
0/18One-command bootstrap
22/22Automated tests
0/11Lint / format config
0/11Static type checking
0/10Reproducible environment
8/10Demonstrated agent practice4 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_files
has_devcontainerno
has_linter_configno
typecheck_configs
agent_commit_share0.04
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
55/55Manageable file sizes0/247 source files over 60KB
Inputs used
primary_languagePHP
largest_source_bytes18,035
source_files_sampled247
oversized_source_files0

Key facts

46GitHub stars
32contributors
101commits, last 12 months
0days since last push
60releases
2bus factor
17open issues
Packagistpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • No resolved dependencies carried a version and a supported ecosystem

More detail

Star and fork history 0 ★ / 67 ⇿
0Stars
67Forks
50Releases

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.

01325385063756632020-092023-092026-08
Major 2Minor 7Patch 39

Each point covers 6 days.

OpenSSF Scorecard 6.3 / 10
6.3aggregate

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-05 15:16 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
8CI-Tests12 out of 14 merged PRs checked by a CI test -- score normalized to 8
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
7Code-ReviewFound 10/14 approved changesets -- score normalized to 7
10Contributorsproject has 11 contributing companies or organizations
n/aDangerous-Workflowno workflows found
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained20 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
n/aPinned-Dependenciesno dependencies found
0SASTSAST tool is not run on all commits -- score normalized to 0
9Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
n/aToken-PermissionsNo tokens found
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 6
RegistryPackageVersion constraintManifest
Packagistdoctrine/doctrine-migrations-bundle^3.3composer.json
Packagistpsr/http-client^1.0composer.json
Packagistsylius-labs/doctrine-migrations-extra-bundle^0.2 || ^0.3composer.json
Packagistsylius/sylius^2.0.1composer.json
Packagistsylius/telemetry^1.0composer.json
Packagistsymfony/mailer^6.4 || ^7.1composer.json
All dependencies 38

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

RegistryPackageVersionRelation
Packagistdoctrine/doctrine-migrations-bundledirect
Packagistpsr/http-clientdirect
Packagistsylius-labs/doctrine-migrations-extra-bundledirect
Packagistsylius/syliusdirect
Packagistsylius/telemetrydirect
Packagistsymfony/mailerdirect
Packagistbehat/behatindirect
Packagistdmore/behat-chrome-extensionindirect
Packagistdmore/chrome-mink-driverindirect
Packagistfriends-of-behat/minkindirect
Packagistfriends-of-behat/mink-browserkit-driverindirect
Packagistfriends-of-behat/mink-debug-extensionindirect
Packagistfriends-of-behat/mink-extensionindirect
Packagistfriends-of-behat/page-object-extensionindirect
Packagistfriends-of-behat/suite-settings-extensionindirect
Packagistfriends-of-behat/symfony-extensionindirect
Packagistfriends-of-behat/variadic-extensionindirect
Packagistlchrusciel/api-test-caseindirect
Packagistmatthiasnoback/symfony-dependency-injection-testindirect
Packagistnyholm/psr7indirect
Packagistphpindirect
Packagistphp-http/discoveryindirect
Packagistphpseclib/phpseclibindirect
Packagistphpstan/phpstanindirect
Packagistphpstan/phpstan-doctrineindirect
Packagistphpstan/phpstan-webmozart-assertindirect
Packagistphpunit/phpunitindirect
Packagistpolishsymfonycommunity/symfony-mocker-containerindirect
Packagistsylius-labs/coding-standardindirect
Packagistsylius/sylius-rectorindirect
Packagistsylius/test-applicationindirect
Packagistsymfony/browser-kitindirect
Packagistsymfony/debug-bundleindirect
Packagistsymfony/dotenvindirect
Packagistsymfony/http-clientindirect
Packagistsymfony/intlindirect
Packagistsymfony/web-profiler-bundleindirect
Packagistsymfony/webpack-encore-bundleindirect
Dependency advisories not assessed

Advisory matching could not run for this report: No resolved dependencies carried a version and a supported ecosystem

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.