Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-10 07:58 UTC

socketry / async

An awesome asynchronous event-driven reactor for Ruby.

RubyMIT★ 2,459 stars⑂ 111 forkssince Apr 2017View on GitHub ↗

socketry/async holds a health index of 92 out of 100, placing it in the Excellent band. It scores highest on Engineering Quality (90/100) and lowest on AI Readiness (58/100). It was last updated 7 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

SocketryOrganization
215 followers199 public repossince Sep 2016

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
RubyGemsasync2.45.1-16912 days ago

Metrics by category

Vitality

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

87Excellent · 21% of overall
How it's scored
36/36Push recency — last push 7 days ago
15.9/36Commit cadence — 23/52 weeks with commits
17.2/18Commit volume — 82 commits in the last year
10/10OpenSSF Scorecard: Maintained — 21 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year82
human_commit_share1
days_since_last_push7
active_weeks_last_year23

Release discipline

100Exceptional
How it's scored
27/27Ships releases — 37 releases published
36/36Release recency — latest release 12 days ago
27/27Release cadence — a release every ~18.2 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count37
latest_release_tagv2.45.1
releases_from_tagsno
days_since_latest_release12
mean_days_between_releases18.2
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?

77Good · 17% of overall
How it's scored
55/60Stars — 2,459 stars
17/25Forks — 111 forks
8.4/15Watchers — 33 watchers
Inputs used
forks111
stars2,459
watchers33
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
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_badges1
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicesgithub.com
has_pull_request_templateyes
How it's scored
80/80Total downloads — 52,851,335 downloads all-time across rubygems
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesasync
dependents—
ecosystemsrubygems
total_downloads52,851,335
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?

67Good · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
1.9/22.5Commit distribution — top contributor authored 91% of commits
13.5/13.5Contributor breadth — 36 contributors
10/10OpenSSF Scorecard: Contributors — project has 9 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled36
top_contributor_share0.914
How it's scored
37.4/42Issue resolution — 89% of issues closed
23.7/30PR acceptance — 170/215 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
3/15OpenSSF Scorecard: Code-Review — Found 8/30 approved changesets -- score normalized to 2
Inputs used
merged_prs170
open_issues20
closed_issues164
prs_merged_7d0
prs_decided_7d0
prs_merged_30d4
prs_decided_30d6
issue_closed_ratio0.891
closed_unmerged_prs45
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
0/20Verified domain
16.8/25Owner reach — 215 followers of socketry
25/25Track record — 199 public repos, account ~10 yr old
Inputs used
followers215
owner_typeOrganization
is_verifiedno
owner_loginsocketry
public_repos199
account_age_days3,650

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on rubygems
35/35Publish recency — latest publish 12 days ago
20/20Version history — 169 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesasync
ecosystemsrubygems
any_deprecatedno
min_days_since_publish12

Engineering Quality

Are baseline engineering and documentation practices in place?

90Excellent · 19% of overall
How it's scored
24/24CI workflows — 10 workflow(s)
24/24Tests present
16/16Linter config — .rubocop.yml
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_testsyes
has_editorconfigyes
has_linter_configyes
has_precommit_configno

Documentation

90Excellent
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage site — https://socketry.github.io/async/
10/10Repository description
10/10Topics — 3 topics
0/10Wiki
Inputs used
topicsruby, async, asynchronous
has_wikino
homepage—
docs_sitehttps://socketry.github.io/async/
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

74Good · 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
1.5/7.5Code-Review — Found 8/30 approved changesets -- score normalized to 2
2.5/2.5Contributors — project has 9 contributing companies or organizations
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
7.5/7.5Maintained — 21 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 10
0/5Packaging — no data
0/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
3.5/5SAST — SAST tool is not run on all commits -- score normalized to 7
5/5Security-Policy — security policy file detected
0/7.5Signed-Releases — no data
7.5/7.5Token-Permissions — GitHub workflow tokens follow principle of least privilege
6.8/7.5Vulnerabilities — 1 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate6.7
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
advisories1
affected_packages1
assessed_packages23
unassessed_packages26
affected_by_severitylow 1
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 23 resolved dependencies against OSV. 26 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.

58Moderate · 4% of overall
How it's scored
45/45Agent instructions — .github/copilot-instructions.md
0/15Machine-readable docs (llms.txt)
13.3/40Legible commit history — 25 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.25
agent_instruction_files.github/copilot-instructions.md
agent_instruction_max_bytes931
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config — .rubocop.yml
0/11Static type checking
10/10Reproducible environment — lockfile
0/10Demonstrated agent practice — no agent-authored commits among the last 100
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_testsyes
lockfilesgems.locked
has_dockerfileno
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configyes
typecheck_configs—
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0
How it's scored
0/45Type-checkable code — Ruby without a type-check config
55/55Manageable file sizes — 0/125 source files over 60KB
Inputs used
primary_languageRuby
largest_source_bytes29,379
source_files_sampled125
oversized_source_files0
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

2,459GitHub stars
36contributors
82commits, last 12 months
7days since last push
37releases
1bus factor
20open 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 ★ / 111 ⇿
0Stars
111Forks
33Releases

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.

02040608010012011042017-042021-112026-07
Major 1Minor 20Patch 12

Each point covers 9 days.

OpenSSF Scorecard 6.7 / 10
6.7aggregate

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-10 07:58 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
2Code-ReviewFound 8/30 approved changesets -- score normalized to 2
10Contributorsproject has 9 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained21 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
7SASTSAST tool is not run on all commits -- score normalized to 7
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
10Token-PermissionsGitHub workflow tokens follow principle of least privilege
9Vulnerabilities1 existing vulnerabilities detected
All dependencies 49

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

RegistryPackageVersionRelation
RubyGemsagent-context—indirect
RubyGemsasync2.1.0indirect
RubyGemsbake-gem—indirect
RubyGemsbake-modernize—indirect
RubyGemsbake-releases—indirect
RubyGemsbake-test—indirect
RubyGemsbake-test-external—indirect
RubyGemsbenchmark-ips—indirect
RubyGemsbenchmark-ips2.13.0indirect
RubyGemsconsole—indirect
RubyGemsconsole1.15.3indirect
RubyGemsconsole1.16.2indirect
RubyGemsconsole1.33.0indirect
RubyGemscovered—indirect
RubyGemsdecode—indirect
RubyGemsfiber-annotation—indirect
RubyGemsfiber-annotation0.2.0indirect
RubyGemsfiber-local1.0.0indirect
RubyGemsfiber-local1.1.0indirect
RubyGemsfiber-profiler—indirect
RubyGemsfiber-storage1.0.1indirect
RubyGemsio-console0.6.0indirect
RubyGemsio-event—indirect
RubyGemsio-event1.0.9indirect
RubyGemsio-event1.13.0indirect
RubyGemsio-event1.2.2indirect
RubyGemsio-event1.6.0indirect
RubyGemsirb1.6.3indirect
RubyGemsjson2.13.2indirect
RubyGemsmetrics—indirect
RubyGemsmetrics0.14.0indirect
RubyGemsopenssl—indirect
RubyGemsreline0.3.2indirect
RubyGemsrubocop—indirect
RubyGemsrubocop-md—indirect
RubyGemsrubocop-socketry—indirect
RubyGemssus—indirect
RubyGemssus0.34.0indirect
RubyGemssus-fixtures-agent-context—indirect
RubyGemssus-fixtures-async—indirect
RubyGemssus-fixtures-benchmark—indirect
RubyGemssus-fixtures-benchmark0.2.1indirect
RubyGemssus-fixtures-console—indirect
RubyGemssus-fixtures-time—indirect
RubyGemstimers4.3.4indirect
RubyGemstimers4.3.5indirect
RubyGemstraces—indirect
RubyGemstraces0.18.1indirect
RubyGemsutopia-project—indirect
Dependency advisories 1

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

PackageVersionRelationSeverityAdvisoriesFixed in
json2.13.2indirectlow12.19.9

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