Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-19 06:50 UTC

y-crdt / yrb

Ruby bindings for yrs.

Ruby · RustMIT★ 97 stars⑂ 12 forkssince May 2022View on GitHub ↗
KindLibraryCommand-line toolhow this is determined

y-crdt/yrb holds a health index of 67 out of 100, placing it in the Good band. It scores highest on Engineering Quality (85/100) and lowest on Vitality (48/100). It was last updated 12 days ago. A single contributor accounts 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

y-crdtOrganization
122 followers18 public repossince Nov 2020

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
RubyGemsy-rb0.7.0-191279 days ago

Metrics by category

Vitality

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

48Weak · 21% of overall
How it's scored
28.8/36Push recency — last push 12 days ago
4/36Commit cadence — 11/52 weeks with commits, discounted for automation: 21 of the last 100 commits human-authored, spanning 260 days
6/18Commit volume — 18 commits in the last year, discounted for automation: 21 of the last 100 commits human-authored, spanning 260 days
1/10OpenSSF Scorecard: Maintained — 2 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 1
Inputs used
commits_last_year18
human_commit_share0.21
days_since_last_push12
active_weeks_last_year11
How it's scored
27/27Ships releases — 23 releases published
0/36Release recency — latest release 952 days ago
27/27Release cadence — a release every ~44.8 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count23
latest_release_tagv0.5.6
releases_from_tagsno
days_since_latest_release952
mean_days_between_releases44.8
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?

53Moderate · 17% of overall
How it's scored
32.2/60Stars — 97 stars
8.7/25Forks — 12 forks
0/15Watchers — 2 watchers
Inputs used
forks12
stars97
watchers2
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
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges0
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services—
has_pull_request_templateno
How it's scored
60.3/80Total downloads — 636,959 downloads all-time across rubygems
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesy-rb
dependents—
ecosystemsrubygems
total_downloads636,959
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?

60Moderate · 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 92% of commits
4.1/13.5Contributor breadth — 3 contributors
10/10OpenSSF Scorecard: Contributors — project has 4 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled3
top_contributor_share0.917
How it's scored
30/42Issue resolution — 71% of issues closed
21.4/30PR acceptance — 173/243 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
10.5/15OpenSSF Scorecard: Code-Review — Found 3/4 approved changesets -- score normalized to 7
Inputs used
merged_prs173
open_issues6
closed_issues15
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.714
closed_unmerged_prs70
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
15/25Owner reach — 122 followers of y-crdt
21.1/25Track record — 18 public repos, account ~5 yr old
Inputs used
followers122
owner_typeOrganization
is_verifiedno
owner_loginy-crdt
public_repos18
account_age_days2,161
How it's scored
25/25Published & resolvable — 1 package(s) on rubygems
26/35Publish recency — latest publish 279 days ago
20/20Version history — 191 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesy-rb
ecosystemsrubygems
any_deprecatedno
min_days_since_publish279

Engineering Quality

Are baseline engineering and documentation practices in place?

85Excellent · 19% of overall
How it's scored
24/24CI workflows — 3 workflow(s)
24/24Tests present
16/16Linter config — .rubocop.yml, .rustfmt.toml
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
12/20OpenSSF Scorecard: CI-Tests — 19 out of 28 merged PRs checked by a CI test -- score normalized to 6
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://y-crdt.github.io/yrb
10/10Repository description
10/10Topics — 4 topics
0/10Wiki
Inputs used
topicscrdt, collaborative-editing, ruby, real-time
has_wikino
homepagehttps://y-crdt.github.io/yrb
docs_sitehttps://y-crdt.github.io/yrb
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

60Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — branch protection not enabled on development/release branches
1.5/2.5CI-Tests — 19 out of 28 merged PRs checked by a CI test -- score normalized to 6
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
5.2/7.5Code-Review — Found 3/4 approved changesets -- score normalized to 7
2.5/2.5Contributors — project has 4 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
0.8/7.5Maintained — 2 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 1
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
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
6/7.5Vulnerabilities — 2 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate5
Excluded from scoring (no data or not applicable): 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
advisories3
affected_packages2
assessed_packages75
unassessed_packages18
affected_by_severitylow 1, unknown 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 75 resolved dependencies against OSV. 18 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.

54Moderate · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
40/40Legible commit history — 16 of 21 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.762
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
12.6/18One-command bootstrap — Cargo.toml, ext/yrb/Cargo.toml (toolchain convention, no task runner)
22/22Automated tests
11/11Lint / format config — .rubocop.yml, .rustfmt.toml
0/11Static type checking
10/10Reproducible environment — lockfile
0/10Demonstrated agent practice — no agent-authored commits among the last 100
8/8Automated maintenance — 79 of the last 100 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfilesCargo.lock
has_dockerfileno
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configyes
typecheck_configs—
agent_commit_share0
toolchain_manifestsCargo.toml, ext/yrb/Cargo.toml
dependency_bot_commit_share0.79
How it's scored
0/45Type-checkable code — Ruby without a type-check config
55/55Manageable file sizes — 0/41 source files over 60KB
Inputs used
primary_languageRuby
largest_source_bytes30,221
source_files_sampled41
oversized_source_files0

Key facts

97GitHub stars
3contributors
18commits, last 12 months
12days since last push
23releases
1bus factor
6open issues
crates.io, RubyGemspackage ecosystems

Data collection warnings

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

More detail

Star and fork history 0 ★ / 12 ⇿
0Stars
12Forks
21Releases

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.

0246810121212022-092024-082026-07
Major 0Minor 4Patch 17

Each point covers 4 days.

OpenSSF Scorecard 5.0 / 10
5.0aggregate

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-10-19 06:50 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
6CI-Tests19 out of 28 merged PRs checked by a CI test -- score normalized to 6
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
7Code-ReviewFound 3/4 approved changesets -- score normalized to 7
10Contributorsproject has 4 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
1Maintained2 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 1
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
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
8Vulnerabilities2 existing vulnerabilities detected
Direct dependencies 11
RegistryPackageVersion constraintManifest
RubyGemsbenchmark—Gemfile
RubyGemsbenchmark-ips—Gemfile
RubyGemsbenchmark-memory—Gemfile
RubyGemsgithub-markup—Gemfile
RubyGemsredcarpet—Gemfile
RubyGemsrspec—Gemfile
RubyGemsrspec-benchmark—Gemfile
RubyGemsrubocop—Gemfile
RubyGemsrubocop-performance—Gemfile
RubyGemsrubocop-rspec—Gemfile
RubyGemsyard—Gemfile
All dependencies 93

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

RegistryPackageVersionRelation
RubyGemsbenchmark—direct
RubyGemsbenchmark-ips—direct
RubyGemsbenchmark-memory—direct
RubyGemsgithub-markup—direct
RubyGemsredcarpet—direct
RubyGemsrspec—direct
RubyGemsrspec-benchmark—direct
RubyGemsrubocop—direct
RubyGemsrubocop-performance—direct
RubyGemsrubocop-rspec—direct
RubyGemsyard—direct
crates.ioaho-corasick1.1.3indirect
crates.ioatomic_refcell0.1.13indirect
crates.iobindgen0.72.1indirect
crates.iobitflags2.8.0indirect
crates.iobumpalo3.17.0indirect
crates.iobyteorder1.5.0indirect
crates.iocexpr0.6.0indirect
crates.iocfg-if1.0.0indirect
crates.ioclang-sys1.8.1indirect
crates.ioeither1.13.0indirect
crates.iogetrandom0.1.16indirect
crates.ioglob0.3.2indirect
crates.ioitertools0.12.1indirect
crates.ioitoa1.0.14indirect
crates.iojs-sys0.3.77indirect
crates.iolazy_static1.5.0indirect
crates.iolibc0.2.169indirect
crates.iolibloading0.8.6indirect
crates.iolog0.4.25indirect
crates.iomagnus—indirect
crates.iomagnus0.8.2indirect
crates.iomagnus-macros0.8.0indirect
crates.iomemchr2.7.4indirect
crates.iominimal-lexical0.2.1indirect
crates.ionom7.1.3indirect
crates.ioonce_cell1.20.2indirect
crates.ioppv-lite860.2.20indirect
crates.ioproc-macro21.0.93indirect
crates.ioquote1.0.38indirect
crates.iorand0.7.3indirect
crates.iorand_chacha0.2.2indirect
crates.iorand_core0.5.1indirect
crates.iorand_hc0.2.0indirect
crates.iorb-sys—indirect
crates.iorb-sys0.9.130indirect
crates.iorb-sys-build0.9.130indirect
crates.iorb-sys-env0.2.3indirect
crates.ioregex1.11.1indirect
crates.ioregex-automata0.4.9indirect
crates.ioregex-syntax0.8.5indirect
crates.iorustc-hash2.1.2indirect
crates.iorustversion1.0.19indirect
crates.ioryu1.0.19indirect
crates.ioseq-macro0.3.5indirect
crates.ioserde1.0.217indirect
crates.ioserde_derive1.0.217indirect
crates.ioserde_json1.0.138indirect
crates.ioshell-words1.1.0indirect
crates.ioshlex1.3.0indirect
crates.iosmallstr0.3.0indirect
crates.iosmallvec1.13.2indirect
crates.iosyn2.0.96indirect
crates.iosyn3.0.2indirect
crates.iothiserror—indirect
crates.iothiserror1.0.69indirect
crates.iothiserror2.0.21indirect
crates.iothiserror-impl1.0.69indirect
crates.iothiserror-impl2.0.21indirect
crates.iounicode-ident1.0.16indirect
crates.iowasi0.9.0+wasi-snapshot-preview1indirect
crates.iowasm-bindgen0.2.100indirect
crates.iowasm-bindgen-backend0.2.100indirect
crates.iowasm-bindgen-macro0.2.100indirect
crates.iowasm-bindgen-macro-support0.2.100indirect
crates.iowasm-bindgen-shared0.2.100indirect
crates.iowindows-targets0.52.6indirect
crates.iowindows_aarch64_gnullvm0.52.6indirect
crates.iowindows_aarch64_msvc0.52.6indirect
crates.iowindows_i686_gnu0.52.6indirect
crates.iowindows_i686_gnullvm0.52.6indirect
crates.iowindows_i686_msvc0.52.6indirect
crates.iowindows_x86_64_gnu0.52.6indirect
crates.iowindows_x86_64_gnullvm0.52.6indirect
crates.iowindows_x86_64_msvc0.52.6indirect
crates.ioy-sync0.4.0indirect
crates.ioyrs0.17.4indirect
crates.iozerocopy0.7.35indirect
crates.iozerocopy-derive0.7.35indirect
RubyGemsbase64—indirect
RubyGemsrake—indirect
RubyGemsrake-compiler—indirect
RubyGemsrb_sys—indirect
Dependency advisories 2

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

PackageVersionRelationSeverityAdvisoriesFixed in
rand0.7.3indirectlow20.10.1
smallstr0.3.0indirectunknown1—

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.