Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-15 04:41 UTC

paypal / paypal-checkout-components

please submit Issues about the PayPal JS SDK here: https://github.com/paypal/paypal-js/issues

JavaScriptApache-2.0★ 1,333 stars⑂ 612 forkssince Aug 2016View on GitHub ↗

paypal/paypal-checkout-components holds a health index of 89 out of 100, placing it in the Excellent band. It scores highest on Engineering Quality (85/100) and lowest on AI Readiness (47/100). It was last updated 3 days ago. 8 contributors account for most of its recent work.

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

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

Ownership

PayPalOrganization
2,038 followers164 public repossince Nov 2010

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
npm@paypal/checkout-components5.0.4342,6376825 days agocross-domaincomponentscomponentkrakenjskraken

Metrics by category

Vitality

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

77Good · 21% of overall
How it's scored
36/36Push recencylast push 3 days ago
25.6/36Commit cadence37/52 weeks with commits
18/18Commit volume129 commits in the last year
0/10OpenSSF Scorecard: Maintainedno data
Inputs used
commits_last_year129
human_commit_share1
days_since_last_push3
active_weeks_last_year37
How it's scored
27/27Ships releases3 releases published
0/36Release recencylatest release 2,861 days ago
27/27Release cadencea release every ~3.5 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count3
latest_release_tagv4.0.234
releases_from_tagsno
days_since_latest_release2,861
mean_days_between_releases3.5

Community & Adoption

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

80Excellent · 17% of overall
How it's scored
50.7/60Stars1,333 stars
23.2/25Forks612 forks
11.5/15Watchers120 watchers
Inputs used
forks612
stars1,333
watchers120
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 (Apache-2.0)
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_badges0
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_services
has_pull_request_templateyes
How it's scored
45.6/80Monthly downloads2,637 downloads/month across npm
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packages@paypal/checkout-components
dependents
ecosystemsnpm
total_downloads
monthly_downloads2,637
unverified_packages_excluded
Excluded from scoring (no data or not applicable): Registry dependents. Remaining weights renormalized.

Sustainability & Governance

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

82Excellent · 23% of overall
How it's scored
54/54Bus factor8 contributor(s) cover half of all commits
19.5/22.5Commit distributiontop contributor authored 13% of commits
13.5/13.5Contributor breadth98 contributors
0/10OpenSSF Scorecard: Contributorsno data
Inputs used
bus_factor8
contributors_sampled98
top_contributor_share0.134
How it's scored
0/42Issue resolutionno issues or no data
23.1/30PR acceptance937/1,216 decided PRs merged
0/13Newcomer PR acceptance0/1 first-time contributors' PRs merged in 30d
0/15OpenSSF Scorecard: Code-Reviewno data
Inputs used
merged_prs937
open_issues0
closed_issues0
prs_merged_7d2
prs_decided_7d2
prs_merged_30d5
prs_decided_30d6
issue_closed_ratio
closed_unmerged_prs279
first_time_authors_30d1
first_time_prs_merged_30d0
first_time_prs_decided_30d1
Excluded from scoring (no data or not applicable): Issue resolution. Remaining weights renormalized.
How it's scored
30/30Ownership backingorganization-owned
0/20Verified domain
23.8/25Owner reach2,038 followers of paypal
25/25Track record164 public repos, account ~15 yr old
Inputs used
followers2,038
owner_typeOrganization
is_verifiedno
owner_loginpaypal
public_repos164
account_age_days5,787

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable1 package(s) on npm
35/35Publish recencylatest publish 5 days ago
20/20Version history682 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packages@paypal/checkout-components
ecosystemsnpm
any_deprecatedno
min_days_since_publish5

Engineering Quality

Are baseline engineering and documentation practices in place?

85Excellent · 19% of overall
How it's scored
24/24CI workflows4 workflow(s)
24/24Tests present
16/16Linter config.eslintrc.js
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Testsno data
Inputs used
has_ciyes
has_testsyes
has_editorconfigyes
has_linter_configyes
has_precommit_configno

Documentation

80Excellent
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage sitehttps://developer.paypal.com/
10/10Repository description
0/10Topics
0/10Wiki
Inputs used
topics
has_wikino
homepage
docs_sitehttps://developer.paypal.com/
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

52Moderate · 16% of overall
How it's scored
30/30Security policy (SECURITY.md)
0/25Dependabot config
0/25Dependency lockfilespublished library — lockfiles are an application concern, not expected
0/20CodeQL workflow
Inputs used
sourcefile_signals
lockfiles
manifestspackage.json
has_codeql_workflowno
has_security_policyyes
has_dependabot_configno
Excluded from scoring (no data or not applicable): Dependency lockfiles. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisoriesno direct dependency carries a known advisory
25/25Indirect dependencies free of known advisoriesno indirect dependency carries a known advisory
0/40No advisories left outstandingno advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages22
unassessed_packages0
affected_by_severitynone
direct_affected_packages0
Excluded from scoring (no data or not applicable): No advisories left outstanding. Remaining weights renormalized. Matched the npm:@paypal/checkout-components@5.0.434 runtime dependency closure — what installing the published package pulls in — 22 packages. 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.

47Weak · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
15/15Machine-readable docs (llms.txt)llms.txt served by the project website (https://developer.paypal.com/llms.txt)
40/40Legible commit history96 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://developer.paypal.com/llms.txt
legible_history_share0.96
agent_instruction_files
agent_instruction_max_bytes
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config.eslintrc.js
0/11Static type checking
0/10Reproducible environment
2/10Demonstrated agent practice1 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_configyes
typecheck_configs
agent_commit_share0.01
toolchain_manifests
dependency_bot_commit_share0
How it's scored
0/45Type-checkable codeJavaScript without a type-check config
55/55Manageable file sizes0/376 source files over 60KB
Inputs used
primary_languageJavaScript
largest_source_bytes49,247
source_files_sampled376
oversized_source_files0

Key facts

1,333GitHub stars
98contributors
129commits, last 12 months
3days since last push
3releases
8bus factor
0open issues
npmpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • OpenSSF Scorecard did not return a usable result (exit code 0; Skipping github.com/paypal/paypal-checkout-components: run: RepoClient.LocalPath: error during tarballHandler.setup: internal error: handler.httpClient.Do: Get "https://codeload.github.com/paypal/paypal-checkout-components/legacy.tar.gz/refs/heads/main": internal error: innerTransport.RoundTrip: internal error: innerTransport.RoundTrip: error in HTTP: dial tcp: lookup codeload.github.com on 127.0.0.11:53: server misbehaving); skipping Scorecard checks

More detail

Star and fork history 0 ★ / 612 ⇿
0Stars
612Forks
3Releases

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.

010020030040050060059072016-112021-102026-09
Major 0Minor 0Patch 3

Each point covers 9 days.

Direct dependencies 13
RegistryPackageVersion constraintManifest
npm@krakenjs/beaver-logger^5.7.0package.json
npm@krakenjs/belter^2.0.0package.json
npm@krakenjs/cross-domain-utils^3.0.0package.json
npm@krakenjs/jsx-pragmatic^3package.json
npm@krakenjs/post-robot^11.0.0package.json
npm@krakenjs/zalgo-promise^2.0.0package.json
npm@krakenjs/zoid^10.6.0package.json
npm@paypal/common-components^1.0.35package.json
npm@paypal/fastlane-sdk-loader^1.2.1package.json
npm@paypal/funding-components^1.0.31package.json
npm@paypal/sdk-client^4.0.199package.json
npm@paypal/sdk-constants^1.0.158package.json
npm@paypal/sdk-logos^2.3.7package.json
All dependencies 49

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

RegistryPackageVersionRelation
npm@krakenjs/beaver-logger^5.7.0direct
npm@krakenjs/belter^2.0.0direct
npm@krakenjs/cross-domain-utils^3.0.0direct
npm@krakenjs/jsx-pragmatic^3direct
npm@krakenjs/post-robot^11.0.0direct
npm@krakenjs/zalgo-promise^2.0.0direct
npm@krakenjs/zoid^10.6.0direct
npm@paypal/common-components^1.0.35direct
npm@paypal/fastlane-sdk-loader^1.2.1direct
npm@paypal/funding-components^1.0.31direct
npm@paypal/sdk-client^4.0.199direct
npm@paypal/sdk-constants^1.0.158direct
npm@paypal/sdk-logos^2.3.7direct
npm@bunchtogether/vite-plugin-flow^1.0.2indirect
npm@krakenjs/eslint-config-grumbler8.1.3indirect
npm@krakenjs/grumbler-scripts^8.1.5indirect
npm@krakenjs/sync-browser-mocks^3.0.0indirect
npm@percy/cli1.28.5indirect
npm@percy/playwright1.1.1indirect
npm@playwright/test^1.38.1indirect
npm@vitest/coverage-v8^1.3.1indirect
npmbabel-core^7.0.0-bridge.0indirect
npmbundlemon^1.1.0indirect
npmconventional-changelog-cli^2.0.34indirect
npmcross-env^7.0.3indirect
npmflow-bin0.155.0indirect
npmflow-remove-types2.246.0indirect
npmflow-typed^3.8.0indirect
npmfs-extra^10.0.0indirect
npmhermes-parser0.23.1indirect
npmhusky^7.0.4indirect
npmimagemagick^0.1.3indirect
npmimgur^0.3.1indirect
npmjest^29.3.1indirect
npmkarma^6.0.0indirect
npmkarma-coverage^2.0.3indirect
npmlint-staged^13.0.0indirect
npmmemory-fs^0.5.0indirect
npmmocha^10.0.0indirect
npmmocketeer^0.3.1indirect
npmpixelmatch^5.2.1indirect
npmplaywright^1.29.1indirect
npmpngjs^6.0.0indirect
npmprettier^3.9.6indirect
npmprettier-plugin-sh^0.19.0indirect
npmpuppeteer^1.20.0indirect
npmserve^14.0.0indirect
npmvite^3.2.4indirect
npmvitest^1.3.1indirect
Dependency advisories 0

Installing npm:@paypal/checkout-components@5.0.434 pulls in 22 packages, direct and transitive: 0 carry known advisories, of which 0 are direct dependencies.

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