Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-11 17:31 UTC

chargebee / chargebee-node

Node.js library for the Chargebee API.

TypeScriptMIT★ 61 stars⑂ 30 forkssince Jan 2014View on GitHub ↗

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

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.

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)

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

Ownership

ChargebeeOrganization · verified domain

186 followers47 public repossince Dec 2010

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

Package ecosystems

Registry	Package	Version	Downloads / mo	Versions	Last publish	Tags
npm	chargebee	3.33.0	819,034	220	2 days ago	payments billings subscription chargebee

Metrics by category

Vitality

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

87Excellent · 21% of overall

Development activity

78Good

How it's scored

36/36	Push recency — last push 2 days ago
18.7/36	Commit cadence — 27/52 weeks with commits
14.4/18	Commit volume — 39 commits in the last year
9/10	OpenSSF Scorecard: Maintained — 11 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 9

Inputs used

commits_last_year	39
human_commit_share	0.99
days_since_last_push	2
active_weeks_last_year	27

Release discipline

100Exceptional

How it's scored

27/27	Ships releases — 39 releases published
36/36	Release recency — latest release 2 days ago
27/27	Release cadence — a release every ~9.5 days
0/10	OpenSSF Scorecard: Signed-Releases — no data

Inputs used

releases_count	39
latest_release_tag	v3.33.0
releases_from_tags	no
days_since_latest_release	2
mean_days_between_releases	9.5

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.8/60	Stars — 61 stars
12.2/25	Forks — 30 forks
8.4/15	Watchers — 33 watchers

Inputs used

forks	30
stars	61
watchers	33
growth_state	unverified
growth_factor_pct	100
growth_unverified_reason	no_history

Community health

57Moderate

How it's scored

22.5/22.5	README
22.5/22.5	License — recognized license (MIT)
0/18	CONTRIBUTING guide
0/13.5	Code of conduct
0/7.2	Issue template
6.3/6.3	PR template

Inputs used

has_readme	yes
has_license	yes
readme_badges	1
has_contributing	no
has_issue_template	no
has_code_of_conduct	no
readme_badge_services	shields.io
has_pull_request_template	yes

Ecosystem adoption (downloads)

98Exceptional

How it's scored

78.8/80	Monthly downloads — 819,034 downloads/month across npm
0/20	Registry dependents — not reported by this ecosystem

Inputs used

packages	chargebee
dependents	—
ecosystems	npm
total_downloads	—
monthly_downloads	819,034
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?

86Excellent · 23% of overall

Maintainer resilience (bus factor)

69Good

How it's scored

36/54	Bus factor — 3 contributor(s) cover half of all commits
16.6/22.5	Commit distribution — top contributor authored 26% of commits
13.5/13.5	Contributor breadth — 23 contributors
3/10	OpenSSF Scorecard: Contributors — project has 1 contributing companies or organizations -- score normalized to 3

Inputs used

bus_factor	3
contributors_sampled	23
top_contributor_share	0.263

Issue & PR responsiveness

90Excellent

How it's scored

40/42	Issue resolution — 95% of issues closed
23.3/30	PR acceptance — 69/89 decided PRs merged
0/13	Newcomer PR acceptance — no first-time contributor's PR decided in 30d
15/15	OpenSSF Scorecard: Code-Review — all changesets reviewed

Inputs used

merged_prs	69
open_issues	2
closed_issues	40
prs_merged_7d	2
prs_decided_7d	2
prs_merged_30d	3
prs_decided_30d	3
issue_closed_ratio	0.952
closed_unmerged_prs	20
first_time_authors_30d	0
first_time_prs_merged_30d	0
first_time_prs_decided_30d	0

Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.

Ownership & stewardship

90Excellent

How it's scored

30/30	Ownership backing — organization-owned
20/20	Verified domain
16.3/25	Owner reach — 186 followers of chargebee
24.2/25	Track record — 47 public repos, account ~15 yr old

Inputs used

followers	186
owner_type	Organization
is_verified	yes
owner_login	chargebee
public_repos	47
account_age_days	5,736

Package maintenance

100Exceptional

How it's scored

25/25	Published & resolvable — 1 package(s) on npm
35/35	Publish recency — latest publish 2 days ago
20/20	Version history — 220 published versions
20/20	Not deprecated — active, not deprecated or yanked

Inputs used

packages	chargebee
ecosystems	npm
any_deprecated	no
min_days_since_publish	2

Engineering Quality

Are baseline engineering and documentation practices in place?

74Good · 19% of overall

Engineering practices

74Good

How it's scored

24/24	CI workflows — 2 workflow(s)
24/24	Tests present
16/16	Linter config — biome.json
0/9.6	Pre-commit hooks
0/6.4	.editorconfig
10/20	OpenSSF Scorecard: CI-Tests — 15 out of 30 merged PRs checked by a CI test -- score normalized to 5

Inputs used

has_ci	yes
has_tests	yes
has_editorconfig	no
has_linter_config	yes
has_precommit_config	no

Documentation

75Good

How it's scored

30/30	README
0/25	Documentation directory
15/15	Documentation / homepage site — https://apidocs.chargebee.com/docs/api?lang=node
10/10	Repository description
10/10	Topics — 3 topics
10/10	Wiki

Inputs used

topics	chargebee, javascript, nodejs
has_wiki	yes
homepage	https://apidocs.chargebee.com/docs/api?lang=node
docs_site	https://apidocs.chargebee.com/docs/api?lang=node
has_readme	yes
has_docs_dir	no
has_description	yes

Security

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

61Moderate · 16% of overall

Security posture

51Moderate

How it's scored

7.5/7.5	Binary-Artifacts — no binaries found in the repo
0.8/7.5	Branch-Protection — branch protection is not maximal on development and all release branches
1.2/2.5	CI-Tests — 15 out of 30 merged PRs checked by a CI test -- score normalized to 5
0/2.5	CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
7.5/7.5	Code-Review — all changesets reviewed
0.8/2.5	Contributors — project has 1 contributing companies or organizations -- score normalized to 3
10/10	Dangerous-Workflow — no dangerous workflow patterns detected
0/7.5	Dependency-Update-Tool — no update tool detected
0/5	Fuzzing — project is not fuzzed
2.5/2.5	License — license file detected
6.8/7.5	Maintained — 11 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 9
5/5	Packaging — packaging workflow detected
2.5/5	Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 5
0/5	SAST — SAST tool is not run on all commits -- score normalized to 0
5/5	Security-Policy — security policy file detected
0/7.5	Signed-Releases — no data
0/7.5	Token-Permissions — detected GitHub workflow tokens with excessive permissions
0/7.5	Vulnerabilities — 15 existing vulnerabilities detected

Inputs used

source	openssf_scorecard
checks_evaluated	17
scorecard_version	v5.5.0
checks_inconclusive	1
scorecard_aggregate	5.1

Excluded from scoring (no data or not applicable): Signed-Releases. Remaining weights renormalized.

Dependency advisories

100Exceptional

How it's scored

35/35	Direct dependencies free of known advisories — no direct dependency carries a known advisory
25/25	Indirect dependencies free of known advisories — no indirect dependency carries a known advisory
0/40	No advisories left outstanding — no advisory carries a publication date

Inputs used

source	osv
advisories	0
affected_packages	0
assessed_packages	1
unassessed_packages	0
affected_by_severity	none
direct_affected_packages	0

Excluded from scoring (no data or not applicable): No advisories left outstanding. Remaining weights renormalized. Matched the npm:chargebee@3.33.0 runtime dependency closure — what installing the published package pulls in — 1 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.

77Good · 4% of overall

Agent context & guidance

43Weak

How it's scored

0/45	Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
15/15	Machine-readable docs (llms.txt) — llms.txt served by the project website (https://apidocs.chargebee.com/llms.txt)
28/40	Legible commit history — 52 of 99 human commits state their intent (structured subject or explanatory body)

Inputs used

has_llms_txt	yes
llms_txt_url	https://apidocs.chargebee.com/llms.txt
legible_history_share	0.525
agent_instruction_files	—
agent_instruction_max_bytes	—

Verify loop (build / test / typecheck)

85Excellent

How it's scored

18/18	One-command bootstrap — Makefile
22/22	Automated tests
11/11	Lint / format config — biome.json
11/11	Static type checking — tsconfig.json
10/10	Reproducible environment — lockfile
8/10	Demonstrated agent practice — 4 of the last 100 commits agent-authored or agent-credited
0/8	Automated maintenance — no automated dependency updates observed
5/10	OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 5

Inputs used

has_nix	no
has_tests	yes
lockfiles	package-lock.json
has_dockerfile	no
typed_language	yes
bootstrap_files	Makefile
has_devcontainer	no
has_linter_config	yes
typecheck_configs	tsconfig.json
agent_commit_share	0.04
toolchain_manifests	—
dependency_bot_commit_share	0

Code legibility for models

98Exceptional

How it's scored

45/45	Type-checkable code — TypeScript (statically typed)
53/55	Manageable file sizes — 9/243 source files over 60KB

Inputs used

primary_language	TypeScript
largest_source_bytes	130,801
source_files_sampled	243
oversized_source_files	9

Machine-readable interfaces

100Exceptional

How it's scored

0/40	API schema (OpenAPI/GraphQL/proto) — not applicable to this kind of software
0/20	MCP server — not applicable to this kind of software
40/40	Runnable examples — examples

Inputs used

example_dirs	examples
has_mcp_signal	no
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

61GitHub stars

23contributors

39commits, last 12 months

2days since last push

39releases

3bus factor

2open issues

npmpackage ecosystems

Data collection warnings

Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token

More detail

Star and fork history 0 ★ / 30 ⇿

0Stars

30Forks

27Releases

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.

Major 0Minor 17Patch 7

Each point covers 10 days.

OpenSSF Scorecard 5.1 / 10

5.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-11 17:31 UTC

10	Binary-Artifacts	no binaries found in the repo
1	Branch-Protection	branch protection is not maximal on development and all release branches
5	CI-Tests	15 out of 30 merged PRs checked by a CI test -- score normalized to 5
0	CII-Best-Practices	no effort to earn an OpenSSF best practices badge detected
10	Code-Review	all changesets reviewed
3	Contributors	project has 1 contributing companies or organizations -- score normalized to 3
10	Dangerous-Workflow	no dangerous workflow patterns detected
0	Dependency-Update-Tool	no update tool detected
0	Fuzzing	project is not fuzzed
10	License	license file detected
9	Maintained	11 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 9
10	Packaging	packaging workflow detected
5	Pinned-Dependencies	dependency not pinned by hash detected -- score normalized to 5
0	SAST	SAST tool is not run on all commits -- score normalized to 0
10	Security-Policy	security policy file detected
n/a	Signed-Releases	no releases found
0	Token-Permissions	detected GitHub workflow tokens with excessive permissions
0	Vulnerabilities	15 existing vulnerabilities detected

Direct dependencies 1

Registry	Package	Version constraint	Manifest
npm	zod	`^4.3.6`	package.json

All dependencies 117

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

Registry	Package	Version	Relation
npm	zod	`4.3.6`	direct
npm	@biomejs/biome	`2.5.7`	indirect
npm	@biomejs/cli-darwin-arm64	`2.5.7`	indirect
npm	@biomejs/cli-darwin-x64	`2.5.7`	indirect
npm	@biomejs/cli-linux-arm64	`2.5.7`	indirect
npm	@biomejs/cli-linux-arm64-musl	`2.5.7`	indirect
npm	@biomejs/cli-linux-x64	`2.5.7`	indirect
npm	@biomejs/cli-linux-x64-musl	`2.5.7`	indirect
npm	@biomejs/cli-win32-arm64	`2.5.7`	indirect
npm	@biomejs/cli-win32-x64	`2.5.7`	indirect
npm	@cspotcode/source-map-support	`0.8.1`	indirect
npm	@jridgewell/resolve-uri	`3.1.2`	indirect
npm	@jridgewell/sourcemap-codec	`1.5.5`	indirect
npm	@jridgewell/trace-mapping	`0.3.9`	indirect
npm	@opentelemetry/api	`1.9.1`	indirect
npm	@tsconfig/node10	`1.0.12`	indirect
npm	@tsconfig/node12	`1.0.11`	indirect
npm	@tsconfig/node14	`1.0.3`	indirect
npm	@tsconfig/node16	`1.0.4`	indirect
npm	@types/chai	`4.3.20`	indirect
npm	@types/mocha	`10.0.10`	indirect
npm	@types/node	`20.12.0`	indirect
npm	acorn	`8.15.0`	indirect
npm	acorn-walk	`8.3.4`	indirect
npm	ansi-colors	`4.1.3`	indirect
npm	ansi-regex	`5.0.1`	indirect
npm	ansi-styles	`4.3.0`	indirect
npm	anymatch	`3.1.3`	indirect
npm	arg	`4.1.3`	indirect
npm	argparse	`2.0.1`	indirect
npm	assertion-error	`1.1.0`	indirect
npm	axios	`^1.12.2`	indirect
npm	balanced-match	`1.0.2`	indirect
npm	binary-extensions	`2.3.0`	indirect
npm	brace-expansion	`2.0.2`	indirect
npm	braces	`3.0.3`	indirect
npm	browser-stdout	`1.3.1`	indirect
npm	camelcase	`6.3.0`	indirect
npm	chai	`4.5.0`	indirect
npm	chalk	`4.1.2`	indirect
npm	chargebee	`^3.15.0`	indirect
npm	check-error	`1.0.3`	indirect
npm	chokidar	`3.6.0`	indirect
npm	cliui	`7.0.4`	indirect
npm	color-convert	`2.0.1`	indirect
npm	color-name	`1.1.4`	indirect
npm	create-require	`1.1.1`	indirect
npm	debug	`4.4.3`	indirect
npm	decamelize	`4.0.0`	indirect
npm	deep-eql	`4.1.4`	indirect
npm	diff	`4.0.4`	indirect
npm	diff	`5.2.2`	indirect
npm	emoji-regex	`8.0.0`	indirect
npm	escalade	`3.2.0`	indirect
npm	escape-string-regexp	`4.0.0`	indirect
npm	fill-range	`7.1.1`	indirect
npm	find-up	`5.0.0`	indirect
npm	flat	`5.0.2`	indirect
npm	fs.realpath	`1.0.0`	indirect
npm	fsevents	`2.3.3`	indirect
npm	get-caller-file	`2.0.5`	indirect
npm	get-func-name	`2.0.2`	indirect
npm	glob	`8.1.0`	indirect
npm	glob-parent	`5.1.2`	indirect
npm	has-flag	`4.0.0`	indirect
npm	he	`1.2.0`	indirect
npm	inflight	`1.0.6`	indirect
npm	inherits	`2.0.4`	indirect
npm	is-binary-path	`2.1.0`	indirect
npm	is-extglob	`2.1.1`	indirect
npm	is-fullwidth-code-point	`3.0.0`	indirect
npm	is-glob	`4.0.3`	indirect
npm	is-number	`7.0.0`	indirect
npm	is-plain-obj	`2.1.0`	indirect
npm	is-unicode-supported	`0.1.0`	indirect
npm	js-yaml	`4.1.1`	indirect
npm	ky	`^1.13.0`	indirect
npm	locate-path	`6.0.0`	indirect
npm	log-symbols	`4.1.0`	indirect
npm	loupe	`2.3.7`	indirect
npm	make-error	`1.3.6`	indirect
npm	minimatch	`5.1.6`	indirect
npm	mocha	`10.8.2`	indirect
npm	ms	`2.1.3`	indirect
npm	normalize-path	`3.0.0`	indirect
npm	once	`1.4.0`	indirect
npm	p-limit	`3.1.0`	indirect
npm	p-locate	`5.0.0`	indirect
npm	path-exists	`4.0.0`	indirect
npm	pathval	`1.1.1`	indirect
npm	picomatch	`2.3.1`	indirect
npm	randombytes	`2.1.0`	indirect
npm	readdirp	`3.6.0`	indirect
npm	require-directory	`2.1.1`	indirect
npm	safe-buffer	`5.2.1`	indirect
npm	serialize-javascript	`6.0.2`	indirect
npm	string-width	`4.2.3`	indirect
npm	strip-ansi	`6.0.1`	indirect
npm	strip-json-comments	`3.1.1`	indirect
npm	supports-color	`7.2.0`	indirect
npm	supports-color	`8.1.1`	indirect
npm	to-regex-range	`5.0.1`	indirect
npm	ts-node	`10.9.2`	indirect
npm	type-detect	`4.1.0`	indirect
npm	typescript	`5.5.4`	indirect
npm	undici-types	`5.26.5`	indirect
npm	undici-types	`7.18.2`	indirect
npm	v8-compile-cache-lib	`3.0.1`	indirect
npm	workerpool	`6.5.1`	indirect
npm	wrap-ansi	`7.0.0`	indirect
npm	wrappy	`1.0.2`	indirect
npm	y18n	`5.0.8`	indirect
npm	yargs	`16.2.0`	indirect
npm	yargs-parser	`20.2.9`	indirect
npm	yargs-unparser	`2.0.0`	indirect
npm	yn	`3.1.1`	indirect
npm	yocto-queue	`0.1.0`	indirect

Dependency advisories 0

Installing npm:chargebee@3.33.0 pulls in 1 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.

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 — npm.

Software health index

Score profile

Ownership

Package ecosystems

Metrics by category

Key facts

Data collection warnings

More detail

Feedback

Related records