Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-11-17 13:05 UTC

ably / specification

The Ably features spec for client library SDKs.

Shell · HTML · CSSApache-2.0★ 2 stars⑂ 3 forkssince Sep 2022View on GitHub ↗

ably/specification holds a health index of 67 out of 100, placing it in the Good band. It scores highest on Sustainability & Governance (77/100) and lowest on Community & Adoption (37/100). It was last updated 1 day ago. 4 contributors account for most of its recent work.

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

67
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 61 is calibrated to 67 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.

Metrics by category

Vitality

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

74Good · 21% of overall
How it's scored
36/36Push recency — last push 1 days ago
29.8/36Commit cadence — 43/52 weeks with commits
18/18Commit volume — 302 commits in the last year
10/10OpenSSF Scorecard: Maintained — 24 commit(s) and 18 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year302
human_commit_share1
days_since_last_push1
active_weeks_last_year43
How it's scored
27/27Ships releases — 3 releases published
0/36Release recency — latest release 1,047 days ago
12.6/27Release cadence — a release every ~179.9 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count3
latest_release_tagv3.0.0
releases_from_tagsno
days_since_latest_release1,047
mean_days_between_releases179.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?

37Weak · 17% of overall
How it's scored
0/60Stars — 2 stars
2.5/25Forks — 3 forks
6.8/15Watchers — 18 watchers
Inputs used
forks3
stars2
watchers18
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_badges1
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_servicesgithub.com
has_pull_request_templateno

Sustainability & Governance

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

77Good · 23% of overall
How it's scored
43.2/54Bus factor — 4 contributor(s) cover half of all commits
17.5/22.5Commit distribution — top contributor authored 22% of commits
13.5/13.5Contributor breadth — 44 contributors
10/10OpenSSF Scorecard: Contributors — project has 26 contributing companies or organizations
Inputs used
bus_factor4
contributors_sampled44
top_contributor_share0.222
How it's scored
6.7/42Issue resolution — 16% of issues closed
25.8/30PR acceptance — 272/316 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_prs272
open_issues180
closed_issues34
prs_merged_7d2
prs_decided_7d2
prs_merged_30d2
prs_decided_30d2
issue_closed_ratio0.159
closed_unmerged_prs44
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.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,265

Engineering Quality

Are baseline engineering and documentation practices in place?

46Weak · 19% of overall
How it's scored
24/24CI workflows — 2 workflow(s)
0/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 11 out of 11 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsno
has_editorconfigyes
has_linter_configno
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
0/10Topics
0/10Wiki
Inputs used
topics—
has_wikino
homepage—
docs_site—
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

66Good · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — no data
2.5/2.5CI-Tests — 11 out of 11 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
7.5/7.5Code-Review — all changesets reviewed
2.5/2.5Contributors — project has 26 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 — 24 commit(s) and 18 issue activity found in the last 90 days -- score normalized to 10
0/5Packaging — no data
1.5/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 3
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 — no data
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
0/7.5Vulnerabilities — 30 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate5.8
Excluded from scoring (no data or not applicable): Branch-Protection, Packaging, Signed-Releases. 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
advisories30
affected_packages12
assessed_packages138
unassessed_packages0
affected_by_severitycritical 1, high 8, moderate 3
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 138 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.

46Weak · 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 — 80 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.8
agent_instruction_filesCLAUDE.md
agent_instruction_max_bytes9,045
How it's scored
0/18One-command bootstrap
0/22Automated tests
0/11Lint / format config
0/11Static type checking
10/10Reproducible environment — lockfile
10/10Demonstrated agent practice — 27 of the last 100 commits agent-authored or agent-credited
0/8Automated maintenance — no automated dependency updates observed
3/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 3
Inputs used
has_nixno
has_testsno
lockfilespackage-lock.json
has_dockerfileno
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configs—
agent_commit_share0.27
toolchain_manifests—
dependency_bot_commit_share0
How it's scored
0/45Type-checkable code — Shell without a type-check config
0/55Manageable file sizes — no source files detected
Inputs used
primary_languageShell
largest_source_bytes—
source_files_sampled0
oversized_source_files0
Excluded from scoring (no data or not applicable): Manageable file sizes. Remaining weights renormalized.

Key facts

2GitHub stars
44contributors
302commits, last 12 months
1days since last push
3releases
4bus factor
180open issues
npmpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • Could not fetch npm package '@ably/specification-build' from its registry

More detail

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

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.

12233312022-112023-042023-09
Major 1Minor 0Patch 0
OpenSSF Scorecard 5.8 / 10
5.8aggregate

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-17 13:04 UTC

10Binary-Artifactsno binaries found in the repo
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-Tests11 out of 11 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
10Code-Reviewall changesets reviewed
10Contributorsproject has 26 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained24 commit(s) and 18 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
3Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 3
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities30 existing vulnerabilities detected
All dependencies 138

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

RegistryPackageVersionRelation
npm@nodelib/fs.scandir2.1.5indirect
npm@nodelib/fs.stat2.0.5indirect
npm@nodelib/fs.walk1.2.8indirect
npmacorn7.4.1indirect
npmacorn-node1.8.2indirect
npmacorn-walk7.2.0indirect
npmansi-styles3.2.1indirect
npmanymatch3.1.2indirect
npmarg5.0.2indirect
npmbalanced-match1.0.2indirect
npmbinary-extensions2.2.0indirect
npmbrace-expansion1.1.11indirect
npmbraces3.0.3indirect
npmcall-bind1.0.2indirect
npmcamelcase-css2.0.1indirect
npmchalk2.4.2indirect
npmchokidar3.5.3indirect
npmcolor-convert1.9.3indirect
npmcolor-name1.1.3indirect
npmcolor-name1.1.4indirect
npmconcat-map0.0.1indirect
npmcross-spawn6.0.5indirect
npmcssesc3.0.0indirect
npmdefine-properties1.1.4indirect
npmdefined1.0.0indirect
npmdetective5.2.1indirect
npmdidyoumean1.2.2indirect
npmdlv1.1.3indirect
npmerror-ex1.3.2indirect
npmes-abstract1.20.3indirect
npmes-to-primitive1.2.1indirect
npmescape-string-regexp1.0.5indirect
npmfast-glob3.2.12indirect
npmfastq1.13.0indirect
npmfill-range7.1.1indirect
npmfsevents2.3.2indirect
npmfunction-bind1.1.1indirect
npmfunction.prototype.name1.1.5indirect
npmfunctions-have-names1.2.3indirect
npmget-intrinsic1.1.3indirect
npmget-symbol-description1.0.0indirect
npmglob-parent5.1.2indirect
npmglob-parent6.0.2indirect
npmgraceful-fs4.2.10indirect
npmhas1.0.3indirect
npmhas-bigints1.0.2indirect
npmhas-flag3.0.0indirect
npmhas-property-descriptors1.0.0indirect
npmhas-symbols1.0.3indirect
npmhas-tostringtag1.0.0indirect
npmhosted-git-info2.8.9indirect
npminternal-slot1.0.3indirect
npmis-arrayish0.2.1indirect
npmis-bigint1.0.4indirect
npmis-binary-path2.1.0indirect
npmis-boolean-object1.1.2indirect
npmis-callable1.2.7indirect
npmis-core-module2.10.0indirect
npmis-date-object1.0.5indirect
npmis-extglob2.1.1indirect
npmis-glob4.0.3indirect
npmis-negative-zero2.0.2indirect
npmis-number7.0.0indirect
npmis-number-object1.0.7indirect
npmis-regex1.1.4indirect
npmis-shared-array-buffer1.0.2indirect
npmis-string1.0.7indirect
npmis-symbol1.0.4indirect
npmis-weakref1.0.2indirect
npmisexe2.0.0indirect
npmjson-parse-better-errors1.0.2indirect
npmlilconfig2.0.6indirect
npmload-json-file4.0.0indirect
npmmemorystream0.3.1indirect
npmmerge21.4.1indirect
npmmicromatch4.0.5indirect
npmminimatch3.1.2indirect
npmminimist1.2.6indirect
npmnanoid3.3.4indirect
npmnice-try1.0.5indirect
npmnormalize-package-data2.5.0indirect
npmnormalize-path3.0.0indirect
npmnpm-run-all4.1.5indirect
npmobject-hash3.0.0indirect
npmobject-inspect1.12.2indirect
npmobject-keys1.1.1indirect
npmobject.assign4.1.4indirect
npmparse-json4.0.0indirect
npmpath-key2.0.1indirect
npmpath-parse1.0.7indirect
npmpath-type3.0.0indirect
npmpicocolors1.0.0indirect
npmpicomatch2.3.1indirect
npmpidtree0.3.1indirect
npmpify2.3.0indirect
npmpify3.0.0indirect
npmpostcss8.4.17indirect
npmpostcss-import14.1.0indirect
npmpostcss-js4.0.0indirect
npmpostcss-load-config3.1.4indirect
npmpostcss-nested5.0.6indirect
npmpostcss-selector-parser6.0.10indirect
npmpostcss-value-parser4.2.0indirect
npmqueue-microtask1.2.3indirect
npmquick-lru5.1.1indirect
npmread-cache1.0.0indirect
npmread-pkg3.0.0indirect
npmreaddirp3.6.0indirect
npmregexp.prototype.flags1.4.3indirect
npmresolve1.22.1indirect
npmreusify1.0.4indirect
npmrun-parallel1.2.0indirect
npmsafe-regex-test1.0.0indirect
npmsemver5.7.1indirect
npmshebang-command1.2.0indirect
npmshebang-regex1.0.0indirect
npmshell-quote1.7.3indirect
npmside-channel1.0.4indirect
npmsource-map-js1.0.2indirect
npmspdx-correct3.1.1indirect
npmspdx-exceptions2.3.0indirect
npmspdx-expression-parse3.0.1indirect
npmspdx-license-ids3.0.12indirect
npmstring.prototype.padend3.1.3indirect
npmstring.prototype.trimend1.0.5indirect
npmstring.prototype.trimstart1.0.5indirect
npmstrip-bom3.0.0indirect
npmsupports-color5.5.0indirect
npmsupports-preserve-symlinks-flag1.0.0indirect
npmtailwindcss3.1.8indirect
npmto-regex-range5.0.1indirect
npmunbox-primitive1.0.2indirect
npmutil-deprecate1.0.2indirect
npmvalidate-npm-package-license3.0.4indirect
npmwhich1.3.1indirect
npmwhich-boxed-primitive1.0.2indirect
npmxtend4.0.2indirect
npmyaml1.10.2indirect
Dependency advisories 12

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

PackageVersionRelationSeverityAdvisoriesFixed in
shell-quote1.7.3indirectcritical21.9.0
brace-expansion1.1.11indirecthigh85.0.12
cross-spawn6.0.5indirecthigh17.0.5
minimatch3.1.2indirecthigh310.2.3
nanoid3.3.4indirecthigh45.1.16
picomatch2.3.1indirecthigh24.0.4
postcss8.4.17indirecthigh58.5.23
semver5.7.1indirecthigh17.5.2
source-map-js1.0.2indirecthigh11.2.2
micromatch4.0.5indirectmoderate14.0.8
postcss-selector-parser6.0.10indirectmoderate17.1.6
yaml1.10.2indirectmoderate12.8.3

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.