Public record
Software health reportschema 0.12.0 · metrics 2.10.0 · 2026-07-17 17:50 UTC

socketry / async

An awesome asynchronous event-driven reactor for Ruby.

RubyMIT★ 2,453 stars⑂ 109 forkssince Apr 2017View on GitHub ↗

socketry/async holds a health index of 86 out of 100, placing it in the Excellent band. It scores highest on Vitality (77/100) and lowest on Security (62/100). It was last updated 15 days ago. A single contributor accounts 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

SocketryOrganization
214 followers185 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.42.0-16415 days ago

Metrics by category

Vitality

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

77Good · 21% of overall
How it's scored
28.8/36Push recencylast push 15 days ago
15.2/36Commit cadence22/52 weeks with commits
18/18Commit volume108 commits in the last year
5/10OpenSSF Scorecard: Maintained6 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 5
Inputs used
commits_last_year108
human_commit_share
days_since_last_push15
active_weeks_last_year22
How it's scored
27/27Ships releases32 releases published
36/36Release recencylatest release 15 days ago
19.8/27Release cadencea release every ~82.1 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count32
latest_release_tagv2.42.0
releases_from_tagsno
days_since_latest_release15
mean_days_between_releases82.1
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/60Stars2,453 stars
16.9/25Forks109 forks
8.3/15Watchers32 watchers
Inputs used
forks109
stars2,453
watchers32
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized 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_badges
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services
has_pull_request_templateyes
How it's scored
80/80Total downloads50,698,448 downloads all-time across rubygems
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagesasync
dependents
ecosystemsrubygems
total_downloads50,698,448
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?

71Good · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
1.8/22.5Commit distributiontop contributor authored 92% of commits
13.5/13.5Contributor breadth35 contributors
10/10OpenSSF Scorecard: Contributorsproject has 9 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled35
top_contributor_share0.919
How it's scored
37.6/42Issue resolution90% of issues closed
23.8/30PR acceptance162/204 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
1.5/15OpenSSF Scorecard: Code-ReviewFound 4/30 approved changesets -- score normalized to 1
Inputs used
merged_prs162
open_issues19
closed_issues163
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio0.896
closed_unmerged_prs42
first_time_authors_30d
first_time_prs_merged_30d
first_time_prs_decided_30d
Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
30/30Ownership backingorganization-owned
0/20Verified domainverified-domain status not read for this organization
16.8/25Owner reach214 followers of socketry
25/25Track record185 public repos, account ~9 yr old
Inputs used
followers214
owner_typeOrganization
is_verified
owner_loginsocketry
public_repos185
account_age_days3,595
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable1 package(s) on rubygems
35/35Publish recencylatest publish 15 days ago
20/20Version history164 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesasync
ecosystemsrubygems
any_deprecatedno
min_days_since_publish15

Engineering Quality

Are baseline engineering and documentation practices in place?

74Good · 19% of overall
How it's scored
24/24CI workflows10 workflow(s)
24/24Tests present
16/16Linter config.rubocop.yml
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests5 out of 5 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

50Moderate
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics3 topics
0/10Wiki
Inputs used
topicsruby, async, asynchronous
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?

62Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionno data
2.5/2.5CI-Tests5 out of 5 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0.8/7.5Code-ReviewFound 4/30 approved changesets -- score normalized to 1
2.5/2.5Contributorsproject has 9 contributing companies or organizations
10/10Dangerous-Workflowno dangerous workflow patterns detected
0/7.5Dependency-Update-Toolno update tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
3.8/7.5Maintained6 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 5
0/5Packagingno data
0/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
3/5SASTSAST tool is not run on all commits -- score normalized to 6
5/5Security-Policysecurity policy file detected
0/7.5Signed-Releasesno data
7.5/7.5Token-PermissionsGitHub workflow tokens follow principle of least privilege
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate6.2
Excluded from scoring (no data or not applicable): Branch-Protection, Packaging, Signed-Releases. Remaining weights renormalized.

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.

67Good · 4% of overall
How it's scored
45/45Agent instructions.github/copilot-instructions.md
0/15Machine-readable docs (llms.txt)
0/40Legible commit historyno data
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share
agent_instruction_files.github/copilot-instructions.md
agent_instruction_max_bytes931
Excluded from scoring (no data or not applicable): Legible commit history. Remaining weights renormalized.
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config.rubocop.yml
0/11Static type checking
10/10Reproducible environmentlockfile
0/10Demonstrated agent practiceno data
0/8Automated maintenanceno data
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency 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_share
toolchain_manifests
dependency_bot_commit_share
Excluded from scoring (no data or not applicable): Demonstrated agent practice, Automated maintenance. Remaining weights renormalized.
How it's scored
0/45Type-checkable codeRuby without a type-check config
55/55Manageable file sizes0/124 source files over 60KB
Inputs used
primary_languageRuby
largest_source_bytes25,850
source_files_sampled124
oversized_source_files0
How it's scored
0/40API schema (OpenAPI/GraphQL/proto)not applicable to this kind of software
0/20MCP servernot applicable to this kind of software
40/40Runnable examplesexamples
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,453GitHub stars
35contributors
108commits, last 12 months
15days since last push
32releases
1bus factor
19open issues
package ecosystems

More detail

OpenSSF Scorecard 6.2 / 10
6.2aggregate

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-07-17 17:50 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-Tests5 out of 5 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
1Code-ReviewFound 4/30 approved changesets -- score normalized to 1
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
5Maintained6 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 5
n/aPackagingpackaging workflow not detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
6SASTSAST tool is not run on all commits -- score normalized to 6
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
10Token-PermissionsGitHub workflow tokens follow principle of least privilege
10Vulnerabilities0 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-contextindirect
RubyGemsasync2.1.0indirect
RubyGemsbake-gemindirect
RubyGemsbake-modernizeindirect
RubyGemsbake-releasesindirect
RubyGemsbake-testindirect
RubyGemsbake-test-externalindirect
RubyGemsbenchmark-ipsindirect
RubyGemsbenchmark-ips2.13.0indirect
RubyGemsconsoleindirect
RubyGemsconsole1.15.3indirect
RubyGemsconsole1.16.2indirect
RubyGemsconsole1.33.0indirect
RubyGemscoveredindirect
RubyGemsdecodeindirect
RubyGemsfiber-annotationindirect
RubyGemsfiber-annotation0.2.0indirect
RubyGemsfiber-local1.0.0indirect
RubyGemsfiber-local1.1.0indirect
RubyGemsfiber-profilerindirect
RubyGemsfiber-storage1.0.1indirect
RubyGemsio-console0.6.0indirect
RubyGemsio-eventindirect
RubyGemsio-event1.0.9indirect
RubyGemsio-event1.13.0indirect
RubyGemsio-event1.2.2indirect
RubyGemsio-event1.6.0indirect
RubyGemsirb1.6.3indirect
RubyGemsjson2.13.2indirect
RubyGemsmetricsindirect
RubyGemsmetrics0.14.0indirect
RubyGemsopensslindirect
RubyGemsreline0.3.2indirect
RubyGemsrubocopindirect
RubyGemsrubocop-mdindirect
RubyGemsrubocop-socketryindirect
RubyGemssusindirect
RubyGemssus0.34.0indirect
RubyGemssus-fixtures-agent-contextindirect
RubyGemssus-fixtures-asyncindirect
RubyGemssus-fixtures-benchmarkindirect
RubyGemssus-fixtures-benchmark0.2.1indirect
RubyGemssus-fixtures-consoleindirect
RubyGemssus-fixtures-timeindirect
RubyGemstimers4.3.4indirect
RubyGemstimers4.3.5indirect
RubyGemstracesindirect
RubyGemstraces0.18.1indirect
RubyGemsutopia-projectindirect
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.12.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statisticsRubyGems.