Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-11-18 11:39 UTC

ably / ably-pubsub-dotnet

.NET, MAUI, Xamarin, Mono and Unity client library SDK for Ably realtime messaging service

C#Apache-2.0★ 51 stars⑂ 20 forkssince Dec 2014View on GitHub ↗

ably/ably-pubsub-dotnet holds a health index of 86 out of 100, placing it in the Excellent band. It scores highest on AI Readiness (91/100) and lowest on Community & Adoption (52/100). It was last updated 2 days ago. 3 contributors account for most of its recent work.

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

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

Ownership

224 followers125 public repossince Jun 2012

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

Package ecosystems

Metrics by category

Vitality

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

76Good · 21% of overall
How it's scored
36/36Push recency — last push 2 days ago
11.8/36Commit cadence — 17/52 weeks with commits
18/18Commit volume — 235 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year235
human_commit_share1
days_since_last_push2
active_weeks_last_year17
How it's scored
27/27Ships releases — 63 releases published
36/36Release recency — latest release 2 days ago
12.6/27Release cadence — a release every ~137 days
0/10OpenSSF Scorecard: Signed-Releases — Project has not signed or included provenance with any releases.
Inputs used
releases_count63
latest_release_tag2.1.0
releases_from_tagsno
days_since_latest_release2
mean_days_between_releases137

Community & Adoption

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

52Moderate · 17% of overall
How it's scored
27.6/60Stars — 51 stars
10.7/25Forks — 20 forks
8/15Watchers — 29 watchers
Inputs used
forks20
stars51
watchers29
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (Apache-2.0)
18/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges3
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_servicesbadgen.net, shields.io
has_pull_request_templateno
How it's scored
28.6/80Total downloads — 569 downloads all-time across nuget
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesAbly.PubSub.Core, Ably.PubSub.Device, Ably.PubSub.Server
dependents—
ecosystemsnuget
total_downloads569
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?

85Excellent · 23% of overall
How it's scored
36/54Bus factor — 3 contributor(s) cover half of all commits
16.3/22.5Commit distribution — top contributor authored 27% of commits
13.5/13.5Contributor breadth — 23 contributors
10/10OpenSSF Scorecard: Contributors — project has 12 contributing companies or organizations
Inputs used
bus_factor3
contributors_sampled23
top_contributor_share0.274
How it's scored
35.4/42Issue resolution — 84% of issues closed
27.2/30PR acceptance — 859/947 decided PRs merged
13/13Newcomer PR acceptance — 2/2 first-time contributors' PRs merged in 30d
9/15OpenSSF Scorecard: Code-Review — Found 6/10 approved changesets -- score normalized to 6
Inputs used
merged_prs859
open_issues67
closed_issues359
prs_merged_7d2
prs_decided_7d2
prs_merged_30d17
prs_decided_30d17
issue_closed_ratio0.843
closed_unmerged_prs88
first_time_authors_30d1
first_time_prs_merged_30d2
first_time_prs_decided_30d2
How it's scored
30/30Ownership backing — organization-owned
20/20Verified domain
16.9/25Owner reach — 224 followers of ably
25/25Track record — 125 public repos, account ~14 yr old
Inputs used
followers224
owner_typeOrganization
is_verifiedyes
owner_loginably
public_repos125
account_age_days5,266
How it's scored
25/25Published & resolvable — 3 package(s) on nuget
35/35Publish recency — latest publish 2 days ago
12/20Version history — 2 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesAbly.PubSub.Core, Ably.PubSub.Device, Ably.PubSub.Server
ecosystemsnuget
any_deprecatedno
min_days_since_publish2

Engineering Quality

Are baseline engineering and documentation practices in place?

70Good · 19% of overall
How it's scored
24/24CI workflows — 8 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 10 out of 10 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigyes
has_linter_configno
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage site — https://ably.com/download
10/10Repository description
10/10Topics — 16 topics
0/10Wiki
Inputs used
topicsclient-library, dotnet, xamarin, mono, realtime, rest, realtime-messaging, unity, sdk, csharp, c-sharp, maui, maui-app, cross-platform, il2cpp-unity, netstandard20
has_wikino
homepagehttps://ably.com/download
docs_sitehttps://ably.com/download
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

69Good · 16% of overall
How it's scored
0.8/7.5Binary-Artifacts — binaries present in source code
0/7.5Branch-Protection — no data
2.5/2.5CI-Tests — 10 out of 10 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
4.5/7.5Code-Review — Found 6/10 approved changesets -- score normalized to 6
2.5/2.5Contributors — project has 12 contributing companies or organizations
10/10Dangerous-Workflow — no dangerous workflow patterns detected
7.5/7.5Dependency-Update-Tool — update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
7.5/7.5Maintained — 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
0/5Packaging — no data
4/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 8
0/5SAST — SAST tool is not run on all commits -- score normalized to 0
0/5Security-Policy — security policy file not detected
0/7.5Signed-Releases — Project has not signed or included provenance with any releases.
7.5/7.5Token-Permissions — GitHub workflow tokens follow principle of least privilege
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate6.1
Excluded from scoring (no data or not applicable): Branch-Protection, Packaging. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisories — no direct dependency carries a known advisory
0/25Indirect dependencies free of known advisories — transitive set not separable from development and test dependencies in this scope
0/40No advisories left outstanding — no advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages21
unassessed_packages3
affected_by_severitynone
direct_affected_packages0
Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories, No advisories left outstanding. Remaining weights renormalized. Matched 21 resolved dependencies against OSV. 3 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list. 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.

91Excellent · 4% of overall
How it's scored
45/45Agent instructions — CLAUDE.md
15/15Machine-readable docs (llms.txt) — llms.txt served by the project website (https://ably.com/llms.txt)
40/40Legible commit history — 82 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://ably.com/llms.txt
legible_history_share0.82
agent_instruction_filesCLAUDE.md
agent_instruction_max_bytes2,568
How it's scored
12.6/18One-command bootstrap — examples/NotificationsPublisher/NotificationsPublisher.csproj, src/Ably.PubSub.Core.NETFramework/Ably.PubSub.Core.NETFramework.csproj, src/Ably.PubSub.Core/Ably.PubSub.Core.csproj (toolchain convention, no task runner)
22/22Automated tests
0/11Lint / format config
11/11Static type checking — C# (statically typed)
10/10Reproducible environment — devcontainer
8/10Demonstrated agent practice — 4 of the last 100 commits agent-authored or agent-credited
5/8Automated maintenance — dependency automation configured, none observed in the sampled commits
8/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 8
Inputs used
has_nixno
has_testsyes
lockfiles—
has_dockerfileno
typed_languageyes
bootstrap_files—
has_devcontaineryes
has_linter_configno
typecheck_configs—
agent_commit_share0.04
toolchain_manifestsexamples/NotificationsPublisher/NotificationsPublisher.csproj, src/Ably.PubSub.Core.NETFramework/Ably.PubSub.Core.NETFramework.csproj, src/Ably.PubSub.Core/Ably.PubSub.Core.csproj, src/Ably.PubSub.Device/Ably.PubSub.Device.csproj, src/Ably.PubSub.Server/Ably.PubSub.Server.csproj, src/Ably.PubSub.Tests.DotNET/Ably.PubSub.Tests.DotNET.csproj, src/Ably.PubSub.Tests.NETFramework/Ably.PubSub.Tests.NETFramework.csproj, tests/PackageConsumption/DeviceApp/DeviceApp.csproj, tests/PackageConsumption/ServerApp/ServerApp.csproj
dependency_bot_commit_share0
How it's scored
45/45Type-checkable code — C# (statically typed)
54.4/55Manageable file sizes — 7/605 source files over 60KB
Inputs used
primary_languageC#
largest_source_bytes103,839
source_files_sampled605
oversized_source_files7
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, samples
Inputs used
example_dirsexamples, samples
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

51GitHub stars
23contributors
235commits, last 12 months
2days since last push
63releases
3bus factor
67open issues
—package ecosystems

Data collection warnings

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

More detail

Star and fork history 0 ★ / 20 ⇿
0Stars
20Forks
61Releases

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.

0481216202012016-012021-052026-09
Major 0Minor 2Patch 45

Each point covers 10 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-11-18 11:38 UTC

1Binary-Artifactsbinaries present in source code
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
10CI-Tests10 out of 10 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
6Code-ReviewFound 6/10 approved changesets -- score normalized to 6
10Contributorsproject has 12 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
8Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 8
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
0Signed-ReleasesProject has not signed or included provenance with any releases.
10Token-PermissionsGitHub workflow tokens follow principle of least privilege
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 31
RegistryPackageVersion constraintManifest
NuGetMsgPack.Cli0.9.2src/Ably.PubSub.Core/Ably.PubSub.Core.csproj
NuGetNewtonsoft.Json13.0.1src/Ably.PubSub.Core/Ably.PubSub.Core.csproj
NuGetStyleCop.Analyzers1.1.118src/Ably.PubSub.Core/Ably.PubSub.Core.csproj
NuGetSystem.Threading.Channels4.6.0src/Ably.PubSub.Core/Ably.PubSub.Core.csproj
NuGetSystem.Threading.Tasks.Extensions4.5.2src/Ably.PubSub.Core/Ably.PubSub.Core.csproj
NuGetMicrosoft.SourceLink.GitHub8.0.0src/Ably.PubSub.Core/Ably.PubSub.Core.csproj
NuGetStyleCop.Analyzers1.1.118src/Ably.PubSub.Device/Ably.PubSub.Device.csproj
NuGetMicrosoft.SourceLink.GitHub8.0.0src/Ably.PubSub.Device/Ably.PubSub.Device.csproj
NuGetStyleCop.Analyzers1.1.118src/Ably.PubSub.Server/Ably.PubSub.Server.csproj
NuGetMicrosoft.SourceLink.GitHub8.0.0src/Ably.PubSub.Server/Ably.PubSub.Server.csproj
NuGetFluentAssertions6.2.0src/Ably.PubSub.Tests.DotNET/Ably.PubSub.Tests.DotNET.csproj
NuGetMicrosoft.NET.Test.Sdk15.5.0src/Ably.PubSub.Tests.DotNET/Ably.PubSub.Tests.DotNET.csproj
NuGetMsgPack.Cli0.9.2src/Ably.PubSub.Tests.DotNET/Ably.PubSub.Tests.DotNET.csproj
NuGetNewtonsoft.Json13.0.1src/Ably.PubSub.Tests.DotNET/Ably.PubSub.Tests.DotNET.csproj
NuGetRichardSzalay.MockHttp5.0.0src/Ably.PubSub.Tests.DotNET/Ably.PubSub.Tests.DotNET.csproj
NuGetStyleCop.Analyzers1.1.118src/Ably.PubSub.Tests.DotNET/Ably.PubSub.Tests.DotNET.csproj
NuGetSystem.Net.Http4.3.4src/Ably.PubSub.Tests.DotNET/Ably.PubSub.Tests.DotNET.csproj
NuGetSystem.Runtime4.3.1src/Ably.PubSub.Tests.DotNET/Ably.PubSub.Tests.DotNET.csproj
NuGetxunit2.4.1src/Ably.PubSub.Tests.DotNET/Ably.PubSub.Tests.DotNET.csproj
NuGetxunit.analyzers0.10.0src/Ably.PubSub.Tests.DotNET/Ably.PubSub.Tests.DotNET.csproj
NuGetxunit.assert2.4.1src/Ably.PubSub.Tests.DotNET/Ably.PubSub.Tests.DotNET.csproj
NuGetxunit.extensibility.execution2.4.1src/Ably.PubSub.Tests.DotNET/Ably.PubSub.Tests.DotNET.csproj
NuGetxunit.runner.console2.4.1src/Ably.PubSub.Tests.DotNET/Ably.PubSub.Tests.DotNET.csproj
NuGetxunit.runner.visualstudio2.4.1src/Ably.PubSub.Tests.DotNET/Ably.PubSub.Tests.DotNET.csproj
NuGetFluentAssertions6.2.0src/Ably.PubSub.Tests.NETFramework/Ably.PubSub.Tests.NETFramework.csproj
NuGetNewtonsoft.Json13.0.1src/Ably.PubSub.Tests.NETFramework/Ably.PubSub.Tests.NETFramework.csproj
NuGetRichardSzalay.MockHttp5.0.0src/Ably.PubSub.Tests.NETFramework/Ably.PubSub.Tests.NETFramework.csproj
NuGetStyleCop.Analyzers1.1.118src/Ably.PubSub.Tests.NETFramework/Ably.PubSub.Tests.NETFramework.csproj
NuGetxunit2.4.1src/Ably.PubSub.Tests.NETFramework/Ably.PubSub.Tests.NETFramework.csproj
NuGetxunit.assert2.4.1src/Ably.PubSub.Tests.NETFramework/Ably.PubSub.Tests.NETFramework.csproj
NuGetxunit.runner.visualstudio2.4.1src/Ably.PubSub.Tests.NETFramework/Ably.PubSub.Tests.NETFramework.csproj
All dependencies 24

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

RegistryPackageVersionRelation
NuGetFluentAssertions6.2.0direct
NuGetMicrosoft.NET.Test.Sdk15.5.0direct
NuGetMicrosoft.SourceLink.GitHub8.0.0direct
NuGetMsgPack.Cli0.9.2direct
NuGetNewtonsoft.Json13.0.1direct
NuGetRichardSzalay.MockHttp5.0.0direct
NuGetStyleCop.Analyzers1.1.118direct
NuGetSystem.Net.Http4.3.4direct
NuGetSystem.Runtime4.3.1direct
NuGetSystem.Threading.Channels4.6.0direct
NuGetSystem.Threading.Tasks.Extensions4.5.2direct
NuGetxunit2.4.1direct
NuGetxunit.analyzers0.10.0direct
NuGetxunit.assert2.4.1direct
NuGetxunit.extensibility.execution2.4.1direct
NuGetxunit.runner.console2.4.1direct
NuGetxunit.runner.visualstudio2.4.1direct
NuGetAbly.PubSub.Core—indirect
NuGetAbly.PubSub.Device—indirect
NuGetAbly.PubSub.Server—indirect
NuGetILRepack.Lib.MSBuild.Task2.0.18indirect
NuGetMicrosoft.CodeQuality.Analyzers2.9.6indirect
NuGetSystem.Runtime.CompilerServices.Unsafe4.5.2indirect
NuGetTerminal.Gui1.3.1indirect
Dependency advisories 0

This repository publishes no package the index resolves, so its own dependency graph was assessed — 21 packages, which also include development and test pins that never ship: 0 carry known advisories, of which 0 are direct. 3 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list.

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