Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-12 14:31 UTC

chargebee / chargebee-dotnet

.NET library for the Chargebee API.

C#MIT★ 26 stars⑂ 25 forkssince Mar 2013View on GitHub ↗

chargebee/chargebee-dotnet holds a health index of 75 out of 100, placing it in the Good band. It scores highest on Sustainability & Governance (83/100) and lowest on Engineering Quality (44/100). It was last updated 15 days ago. 3 contributors account for most of its recent work.

75
overall / 100
Good

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.

75
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 65 is calibrated to 75 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

RegistryPackageVersionDownloads / moVersionsLast publish
NuGetchargebee3.51.1-24015 days ago

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 15 days ago
11.1/36Commit cadence — 16/52 weeks with commits
12.2/18Commit volume — 22 commits in the last year
5/10OpenSSF Scorecard: Maintained — 7 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 5
Inputs used
commits_last_year22
human_commit_share0.99
days_since_last_push15
active_weeks_last_year16

Release discipline

100Exceptional
How it's scored
27/27Ships releases — 19 releases published
36/36Release recency — latest release 15 days ago
27/27Release cadence — a release every ~19.9 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count19
latest_release_tagv3.51.1
releases_from_tagsno
days_since_latest_release15
mean_days_between_releases19.9
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?

59Moderate · 17% of overall
How it's scored
22.7/60Stars — 26 stars
11.5/25Forks — 25 forks
8.8/15Watchers — 40 watchers
Inputs used
forks25
stars26
watchers40
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonbelow_threshold
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_badges3
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicesshields.io
has_pull_request_templateyes
How it's scored
70.2/80Total downloads — 5,725,196 downloads all-time across nuget
0/20Registry dependents — not reported by this ecosystem
Inputs used
packageschargebee
dependents—
ecosystemsnuget
total_downloads5,725,196
monthly_downloads—
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?

83Excellent · 23% of overall
How it's scored
36/54Bus factor — 3 contributor(s) cover half of all commits
16.4/22.5Commit distribution — top contributor authored 27% of commits
13.5/13.5Contributor breadth — 21 contributors
3/10OpenSSF Scorecard: Contributors — project has 1 contributing companies or organizations -- score normalized to 3
Inputs used
bus_factor3
contributors_sampled21
top_contributor_share0.269
How it's scored
35.7/42Issue resolution — 85% of issues closed
19.8/30PR acceptance — 31/47 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
13.5/15OpenSSF Scorecard: Code-Review — Found 24/25 approved changesets -- score normalized to 9
Inputs used
merged_prs31
open_issues8
closed_issues45
prs_merged_7d0
prs_decided_7d0
prs_merged_30d2
prs_decided_30d3
issue_closed_ratio0.849
closed_unmerged_prs16
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
20/20Verified domain
16.3/25Owner reach — 186 followers of chargebee
24.2/25Track record — 47 public repos, account ~15 yr old
Inputs used
followers186
owner_typeOrganization
is_verifiedyes
owner_loginchargebee
public_repos47
account_age_days5,736

Package maintenance

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

Engineering Quality

Are baseline engineering and documentation practices in place?

44Weak · 19% of overall
How it's scored
24/24CI workflows — 1 workflow(s)
0/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests — 0 out of 25 merged PRs checked by a CI test -- score normalized to 0
Inputs used
has_ciyes
has_testsno
has_editorconfigno
has_linter_configno
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage site — https://apidocs.chargebee.com/docs/api?lang=dotnet
10/10Repository description
10/10Topics — 2 topics
10/10Wiki
Inputs used
topicschargebee, dotnet
has_wikiyes
homepagehttps://apidocs.chargebee.com/docs/api?lang=dotnet
docs_sitehttps://apidocs.chargebee.com/docs/api?lang=dotnet
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

62Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
3.8/7.5Branch-Protection — branch protection is not maximal on development and all release branches
0/2.5CI-Tests — 0 out of 25 merged PRs checked by a CI test -- score normalized to 0
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
6.8/7.5Code-Review — Found 24/25 approved changesets -- score normalized to 9
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
3.8/7.5Maintained — 7 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 5
5/5Packaging — packaging workflow detected
0/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
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
6.8/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate6.1
Excluded from scoring (no data or not applicable): Signed-Releases. Remaining weights renormalized.
How it's scored
14/35Direct dependencies free of known advisories — 1 affected: Newtonsoft.Json 4.5.11 (high 7.5)
0/25Indirect dependencies free of known advisories — transitive set not separable from development and test dependencies in this scope
33.7/40No advisories left outstanding — 1 advisory-carrying package(s) unaddressed past 90 days; oldest published 1,542 days ago
Inputs used
sourceosv
advisories1
affected_packages1
assessed_packages11
unassessed_packages0
affected_by_severityhigh 1
direct_affected_packages1
Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories. Remaining weights renormalized. Matched 11 resolved dependencies against OSV. 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.

47Weak · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
15/15Machine-readable docs (llms.txt) — llms.txt served by the project website (https://apidocs.chargebee.com/llms.txt)
23.7/40Legible commit history — 44 of 99 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://apidocs.chargebee.com/llms.txt
legible_history_share0.444
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
18/18One-command bootstrap — Makefile
0/22Automated tests
0/11Lint / format config
11/11Static type checking — C# (statically typed)
0/10Reproducible environment
4/10Demonstrated agent practice — 2 of the last 100 commits agent-authored or agent-credited
0/8Automated maintenance — no automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsno
lockfiles—
has_dockerfileno
typed_languageyes
bootstrap_filesMakefile
has_devcontainerno
has_linter_configno
typecheck_configs—
agent_commit_share0.02
toolchain_manifestsChargeBee/ChargeBee.csproj, Chargebee.Tests/Chargebee.Tests.csproj
dependency_bot_commit_share0
How it's scored
45/45Type-checkable code — C# (statically typed)
53.3/55Manageable file sizes — 8/258 source files over 60KB
Inputs used
primary_languageC#
largest_source_bytes315,765
source_files_sampled258
oversized_source_files8

Key facts

26GitHub stars
21contributors
22commits, last 12 months
15days since last push
19releases
3bus factor
8open issues
NuGetpackage ecosystems

Data collection warnings

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

More detail

Star and fork history 26 ★ / 25 ⇿
26Stars
25Forks
10Releases

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 2026-03-25. 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.

0510152025252522014-042020-042026-03
Major 0Minor 10Patch 0

Each point covers 11 days.

OpenSSF Scorecard 6.1 / 10
6.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 14:30 UTC

10Binary-Artifactsno binaries found in the repo
5Branch-Protectionbranch protection is not maximal on development and all release branches
0CI-Tests0 out of 25 merged PRs checked by a CI test -- score normalized to 0
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
9Code-ReviewFound 24/25 approved changesets -- score normalized to 9
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
5Maintained7 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 5
10Packagingpackaging workflow detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0SASTSAST tool is not run on all commits -- score normalized to 0
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
9Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 9
RegistryPackageVersion constraintManifest
NuGetMicrosoft.NETFramework.ReferenceAssemblies1.0.0ChargeBee/ChargeBee.csproj
NuGetNewtonsoft.Json13.0.1ChargeBee/ChargeBee.csproj
NuGetSystem.Net.Http4.3.4ChargeBee/ChargeBee.csproj
NuGetSystem.Net.Requests4.3.0ChargeBee/ChargeBee.csproj
NuGetcoverlet.collector6.0.2Chargebee.Tests/Chargebee.Tests.csproj
NuGetMicrosoft.NET.Test.Sdk17.11.1Chargebee.Tests/Chargebee.Tests.csproj
NuGetMoq4.20.70Chargebee.Tests/Chargebee.Tests.csproj
NuGetxunit2.9.2Chargebee.Tests/Chargebee.Tests.csproj
NuGetxunit.runner.visualstudio2.8.2Chargebee.Tests/Chargebee.Tests.csproj
All dependencies 11

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

RegistryPackageVersionRelation
NuGetcoverlet.collector6.0.2direct
NuGetMicrosoft.NET.Test.Sdk17.11.1direct
NuGetMicrosoft.NETFramework.ReferenceAssemblies1.0.0direct
NuGetMoq4.20.70direct
NuGetNewtonsoft.Json13.0.1direct
NuGetNewtonsoft.Json4.5.11direct
NuGetSystem.Net.Http4.3.4direct
NuGetSystem.Net.Requests4.3.0direct
NuGetxunit2.9.2direct
NuGetxunit.runner.visualstudio2.8.2direct
NuGetNUnit2.6.2indirect
Dependency advisories 1

This repository publishes no package the index resolves, so its own dependency graph was assessed — 11 packages, which also include development and test pins that never ship: 1 carry known advisories, of which 1 are direct.

PackageVersionRelationSeverityAdvisoriesFixed in
Newtonsoft.Json4.5.11directhigh113.0.1

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