Public record
Software health reportschema 0.15.0 · metrics 2.10.0 · 2026-07-19 23:01 UTC

chargebee / chargebee-node

Node.js library for the Chargebee API.

TypeScriptMIT★ 60 stars⑂ 30 forkssince Jan 2014View on GitHub ↗
KindLibraryhow this is determined
#chargebee#javascript#nodejs

chargebee/chargebee-node holds a health index of 83 out of 100, placing it in the Excellent band. It scores highest on Vitality (85/100) and lowest on Security (50/100). It was last updated 3 days ago. 3 contributors account for most of its recent work.

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

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

Ownership

ChargebeeOrganization
179 followers45 public repossince Dec 2010

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
npmchargebee3.28.1879,8042143 days agopaymentsbillingssubscriptionchargebee

Metrics by category

Vitality

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

85Excellent · 21% of overall

Development activity

75Good
How it's scored
36/36Push recency — last push 3 days ago
16.6/36Commit cadence — 24/52 weeks with commits
14.2/18Commit volume — 37 commits in the last year
8/10OpenSSF Scorecard: Maintained — 9 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 8
Inputs used
commits_last_year37
human_commit_share—
days_since_last_push3
active_weeks_last_year24

Release discipline

100Exceptional
How it's scored
27/27Ships releases — 33 releases published
36/36Release recency — latest release 3 days ago
27/27Release cadence — a release every ~12.3 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count33
latest_release_tagv3.28.1
releases_from_tagsno
days_since_latest_release3
mean_days_between_releases12.3
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?

64Moderate · 17% of overall

Popularity & adoption

49Weak
How it's scored
28.7/60Stars — 60 stars
12.2/25Forks — 30 forks
8.4/15Watchers — 33 watchers
Inputs used
forks30
stars60
watchers33
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

57Moderate
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
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges—
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services—
has_pull_request_templateyes

Ecosystem adoption (downloads)

99Exceptional
How it's scored
79.3/80Monthly downloads — 879,804 downloads/month across npm
0/20Registry dependents — not reported by this ecosystem
Inputs used
packageschargebee
dependents—
ecosystemsnpm
total_downloads—
monthly_downloads879,804
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?

85Excellent · 23% of overall

Maintainer resilience (bus factor)

69Good
How it's scored
36/54Bus factor — 3 contributor(s) cover half of all commits
16.8/22.5Commit distribution — top contributor authored 25% of commits
13.5/13.5Contributor breadth — 23 contributors
3/10OpenSSF Scorecard: Contributors — project has 1 contributing companies or organizations -- score normalized to 3
Inputs used
bus_factor3
contributors_sampled23
top_contributor_share0.252

Issue & PR responsiveness

90Excellent
How it's scored
40/42Issue resolution — 95% of issues closed
23.2/30PR acceptance — 62/80 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
15/15OpenSSF Scorecard: Code-Review — all changesets reviewed
Inputs used
merged_prs62
open_issues2
closed_issues40
prs_merged_7d—
prs_decided_7d—
prs_merged_30d—
prs_decided_30d—
issue_closed_ratio0.952
closed_unmerged_prs18
first_time_authors_30d—
first_time_prs_merged_30d—
first_time_prs_decided_30d—
Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.

Ownership & stewardship

88Excellent
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain — verified-domain status not read for this organization
16.2/25Owner reach — 179 followers of chargebee
24.1/25Track record — 45 public repos, account ~15 yr old
Inputs used
followers179
owner_typeOrganization
is_verified—
owner_loginchargebee
public_repos45
account_age_days5,682
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on npm
35/35Publish recency — latest publish 3 days ago
20/20Version history — 214 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packageschargebee
ecosystemsnpm
any_deprecatedno
min_days_since_publish3

Engineering Quality

Are baseline engineering and documentation practices in place?

61Moderate · 19% of overall

Engineering practices

52Moderate
How it's scored
24/24CI workflows — 2 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
4/20OpenSSF Scorecard: CI-Tests — 8 out of 30 merged PRs checked by a CI test -- score normalized to 2
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno

Documentation

75Good
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage site — https://apidocs.chargebee.com/docs/api?lang=node
10/10Repository description
10/10Topics — 3 topics
10/10Wiki
Inputs used
topicschargebee, javascript, nodejs
has_wikiyes
homepagehttps://apidocs.chargebee.com/docs/api?lang=node
docs_sitehttps://apidocs.chargebee.com/docs/api?lang=node
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

50Moderate · 16% of overall

Security posture

50Moderate
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0.8/7.5Branch-Protection — branch protection is not maximal on development and all release branches
0.5/2.5CI-Tests — 8 out of 30 merged PRs checked by a CI test -- score normalized to 2
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
7.5/7.5Code-Review — all changesets reviewed
0.8/2.5Contributors — project has 1 contributing companies or organizations -- score normalized to 3
10/10Dangerous-Workflow — no dangerous workflow patterns detected
0/7.5Dependency-Update-Tool — no update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
6/7.5Maintained — 9 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 8
5/5Packaging — packaging workflow detected
2.5/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 5
0/5SAST — SAST tool is not run on all commits -- score normalized to 0
5/5Security-Policy — security policy file detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
0.8/7.5Vulnerabilities — 9 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate5
Excluded from scoring (no data or not applicable): Signed-Releases. 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.

62Moderate · 4% of overall

Agent context & guidance

1Critical
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
0/40Legible commit history — no data
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share—
agent_instruction_files—
agent_instruction_max_bytes—
Excluded from scoring (no data or not applicable): Legible commit history. Remaining weights renormalized.

Verify loop (build / test / typecheck)

80Excellent
How it's scored
18/18One-command bootstrap — Makefile
22/22Automated tests
0/11Lint / format config
11/11Static type checking — tsconfig.json
10/10Reproducible environment — lockfile
0/10Demonstrated agent practice — no data
0/8Automated maintenance — no data
5/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 5
Inputs used
has_nixno
has_testsyes
lockfilespackage-lock.json
has_dockerfileno
typed_languageyes
bootstrap_filesMakefile
has_devcontainerno
has_linter_configno
typecheck_configstsconfig.json
agent_commit_share—
toolchain_manifests—
dependency_bot_commit_share—
Excluded from scoring (no data or not applicable): Demonstrated agent practice, Automated maintenance. Remaining weights renormalized.

Code legibility for models

98Exceptional
How it's scored
45/45Type-checkable code — TypeScript (statically typed)
53/55Manageable file sizes — 8/223 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes128,634
source_files_sampled223
oversized_source_files8

Machine-readable interfaces

100Exceptional
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

60GitHub stars
23contributors
37commits, last 12 months
3days since last push
33releases
3bus factor
2open issues
npmpackage ecosystems

More detail

OpenSSF Scorecard 5.0 / 10
5.0aggregate

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-07-19 23:00 UTC

10Binary-Artifactsno binaries found in the repo
1Branch-Protectionbranch protection is not maximal on development and all release branches
2CI-Tests8 out of 30 merged PRs checked by a CI test -- score normalized to 2
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
10Code-Reviewall changesets reviewed
3Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
8Maintained9 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 8
10Packagingpackaging workflow detected
5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 5
0SASTSAST tool is not run on all commits -- score normalized to 0
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
1Vulnerabilities9 existing vulnerabilities detected
Direct dependencies 1
RegistryPackageVersion constraintManifest
npmzod^4.3.6package.json
All dependencies 109

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

RegistryPackageVersionRelation
npmzod4.3.6direct
npm@cspotcode/source-map-support0.8.1indirect
npm@jridgewell/resolve-uri3.1.2indirect
npm@jridgewell/sourcemap-codec1.5.5indirect
npm@jridgewell/trace-mapping0.3.9indirect
npm@opentelemetry/api1.9.1indirect
npm@tsconfig/node101.0.12indirect
npm@tsconfig/node121.0.11indirect
npm@tsconfig/node141.0.3indirect
npm@tsconfig/node161.0.4indirect
npm@types/chai4.3.20indirect
npm@types/mocha10.0.10indirect
npm@types/node20.12.0indirect
npmacorn8.15.0indirect
npmacorn-walk8.3.4indirect
npmansi-colors4.1.3indirect
npmansi-regex5.0.1indirect
npmansi-styles4.3.0indirect
npmanymatch3.1.3indirect
npmarg4.1.3indirect
npmargparse2.0.1indirect
npmassertion-error1.1.0indirect
npmaxios^1.12.2indirect
npmbalanced-match1.0.2indirect
npmbinary-extensions2.3.0indirect
npmbrace-expansion2.0.2indirect
npmbraces3.0.3indirect
npmbrowser-stdout1.3.1indirect
npmcamelcase6.3.0indirect
npmchai4.5.0indirect
npmchalk4.1.2indirect
npmchargebee^3.15.0indirect
npmcheck-error1.0.3indirect
npmchokidar3.6.0indirect
npmcliui7.0.4indirect
npmcolor-convert2.0.1indirect
npmcolor-name1.1.4indirect
npmcreate-require1.1.1indirect
npmdebug4.4.3indirect
npmdecamelize4.0.0indirect
npmdeep-eql4.1.4indirect
npmdiff4.0.4indirect
npmdiff5.2.2indirect
npmemoji-regex8.0.0indirect
npmescalade3.2.0indirect
npmescape-string-regexp4.0.0indirect
npmfill-range7.1.1indirect
npmfind-up5.0.0indirect
npmflat5.0.2indirect
npmfs.realpath1.0.0indirect
npmfsevents2.3.3indirect
npmget-caller-file2.0.5indirect
npmget-func-name2.0.2indirect
npmglob8.1.0indirect
npmglob-parent5.1.2indirect
npmhas-flag4.0.0indirect
npmhe1.2.0indirect
npminflight1.0.6indirect
npminherits2.0.4indirect
npmis-binary-path2.1.0indirect
npmis-extglob2.1.1indirect
npmis-fullwidth-code-point3.0.0indirect
npmis-glob4.0.3indirect
npmis-number7.0.0indirect
npmis-plain-obj2.1.0indirect
npmis-unicode-supported0.1.0indirect
npmjs-yaml4.1.1indirect
npmky^1.13.0indirect
npmlocate-path6.0.0indirect
npmlog-symbols4.1.0indirect
npmloupe2.3.7indirect
npmmake-error1.3.6indirect
npmminimatch5.1.6indirect
npmmocha10.8.2indirect
npmms2.1.3indirect
npmnormalize-path3.0.0indirect
npmonce1.4.0indirect
npmp-limit3.1.0indirect
npmp-locate5.0.0indirect
npmpath-exists4.0.0indirect
npmpathval1.1.1indirect
npmpicomatch2.3.1indirect
npmprettier3.3.3indirect
npmrandombytes2.1.0indirect
npmreaddirp3.6.0indirect
npmrequire-directory2.1.1indirect
npmsafe-buffer5.2.1indirect
npmserialize-javascript6.0.2indirect
npmstring-width4.2.3indirect
npmstrip-ansi6.0.1indirect
npmstrip-json-comments3.1.1indirect
npmsupports-color7.2.0indirect
npmsupports-color8.1.1indirect
npmto-regex-range5.0.1indirect
npmts-node10.9.2indirect
npmtype-detect4.1.0indirect
npmtypescript5.5.4indirect
npmundici-types5.26.5indirect
npmundici-types7.18.2indirect
npmv8-compile-cache-lib3.0.1indirect
npmworkerpool6.5.1indirect
npmwrap-ansi7.0.0indirect
npmwrappy1.0.2indirect
npmy18n5.0.8indirect
npmyargs16.2.0indirect
npmyargs-parser20.2.9indirect
npmyargs-unparser2.0.0indirect
npmyn3.1.1indirect
npmyocto-queue0.1.0indirect
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.

Related records

Inspected repositories sharing catalogue tags or ecosystems with chargebee/chargebee-node. Read them side by side →

95graphql-hive/graphql-yoga🧘 Rewrite of a fully-featured GraphQL Server with focus on easy setup, performance & great developer experience. The core of Yoga implements WHATWG Fetch API and can run/deploy on any JS environment.Exceptional100Azure/azure-sdk-for-jsThis repository is for active development of the Azure SDK for JavaScript (NodeJS & Browser). For consumers of the SDK we recommend visiting our public developer docs at https://docs.microsoft.com/javascript/azure/ or our versioned developer docs at https://azure.github.io/azure-sdk-for-js. Exceptional100DataDog/dd-trace-jsDatadog APM client for Node.jsExceptional99electron/electron:electron: Build cross-platform desktop apps with JavaScript, HTML, and CSSExceptional99axios/axiosPromise based HTTP client for the browser and node.jsExceptional98mastra-ai/mastraMastra is the modern TypeScript framework for AI-powered applications and agents.Exceptional

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.15.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statistics — npm.