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

msgpack / msgpack-ruby

MessagePack implementation for Ruby / msgpack.org[Ruby]

Ruby · C · JavaApache-2.0★ 790 stars⑂ 124 forkssince Sep 2011View on GitHub ↗

msgpack/msgpack-ruby holds a health index of 83 out of 100, placing it in the Excellent band. It scores highest on Sustainability & Governance (82/100) and lowest on AI Readiness (46/100). It was last updated 7 days ago. 3 contributors account for most of its recent work.

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

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

Ownership

MessagePackOrganization
276 followers22 public repossince Feb 2010

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
RubyGemsmsgpack1.8.4-26243 days ago

Metrics by category

Vitality

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

71Good · 21% of overall
How it's scored
36/36Push recency — last push 7 days ago
9.7/36Commit cadence — 14/52 weeks with commits
15/18Commit volume — 46 commits in the last year
10/10OpenSSF Scorecard: Maintained — 28 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year46
human_commit_share1
days_since_last_push7
active_weeks_last_year14
How it's scored
16.2/27Ships releases — 69 version tags (no GitHub releases)
36/36Release recency — latest release 43 days ago
12.6/27Release cadence — a release every ~129.5 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count69
latest_release_tagv1.8.4
releases_from_tagsyes
days_since_latest_release43
mean_days_between_releases129.5
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?

71Good · 17% of overall
How it's scored
47/60Stars — 790 stars
17.4/25Forks — 124 forks
7.1/15Watchers — 20 watchers
Inputs used
forks124
stars790
watchers20
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)
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
80/80Total downloads — 515,676,762 downloads all-time across rubygems
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesmsgpack
dependents—
ecosystemsrubygems
total_downloads515,676,762
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?

82Excellent · 23% of overall
How it's scored
36/54Bus factor — 3 contributor(s) cover half of all commits
15.4/22.5Commit distribution — top contributor authored 32% of commits
13.5/13.5Contributor breadth — 78 contributors
10/10OpenSSF Scorecard: Contributors — project has 87 contributing companies or organizations
Inputs used
bus_factor3
contributors_sampled78
top_contributor_share0.316
How it's scored
41.3/42Issue resolution — 98% of issues closed
23.7/30PR acceptance — 223/282 decided PRs merged
13/13Newcomer PR acceptance — 2/2 first-time contributors' PRs merged in 30d
9/15OpenSSF Scorecard: Code-Review — Found 10/16 approved changesets -- score normalized to 6
Inputs used
merged_prs223
open_issues2
closed_issues119
prs_merged_7d0
prs_decided_7d0
prs_merged_30d3
prs_decided_30d3
issue_closed_ratio0.983
closed_unmerged_prs59
first_time_authors_30d1
first_time_prs_merged_30d2
first_time_prs_decided_30d2
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain
17.6/25Owner reach — 276 followers of msgpack
21.9/25Track record — 22 public repos, account ~16 yr old
Inputs used
followers276
owner_typeOrganization
is_verifiedno
owner_loginmsgpack
public_repos22
account_age_days6,060

Package maintenance

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

Engineering Quality

Are baseline engineering and documentation practices in place?

76Good · 19% of overall
How it's scored
24/24CI workflows — 1 workflow(s)
24/24Tests present
16/16Linter config — .rubocop.yml
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 12 out of 12 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage site — http://msgpack.org/
10/10Repository description
10/10Topics — 1 topics
0/10Wiki
Inputs used
topicsmsgpack
has_wikino
homepagehttp://msgpack.org/
docs_sitehttp://msgpack.org/
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

52Moderate · 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 — 12 out of 12 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 10/16 approved changesets -- score normalized to 6
2.5/2.5Contributors — project has 87 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 — 28 commit(s) and 0 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
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
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate5.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.

46Weak · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
15/15Machine-readable docs (llms.txt) — llms.txt served by the project website (https://redis.io/llms.txt)
30.9/40Legible commit history — 58 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://redis.io/llms.txt
legible_history_share0.58
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config — .rubocop.yml
0/11Static type checking
0/10Reproducible environment
10/10Demonstrated agent practice — 6 of the last 100 commits agent-authored or agent-credited
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
lockfiles—
has_dockerfileno
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configyes
typecheck_configs—
agent_commit_share0.06
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/82 source files over 60KB
Inputs used
primary_languageRuby
largest_source_bytes29,368
source_files_sampled82
oversized_source_files0

Key facts

790GitHub stars
78contributors
46commits, last 12 months
7days since last push
69releases
3bus factor
2open issues
RubyGemspackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • No resolved dependencies carried a version and a supported ecosystem

More detail

Star and fork history 0 ★ / 124 ⇿
0Stars
124Forks
69Releases

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.

02040608010012011742012-052019-062026-08
Major 1Minor 11Patch 57

Each point covers 14 days.

OpenSSF Scorecard 5.2 / 10
5.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-09-10 07:55 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-Tests12 out of 12 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 10/16 approved changesets -- score normalized to 6
10Contributorsproject has 87 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained28 commit(s) and 0 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
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
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 9
RegistryPackageVersion constraintManifest
RubyGemsrubocop~> 0.82.0Gemfile
RubyGemssimplecov—Gemfile
RubyGemsrake—Gemfile
RubyGemsrake-compiler>= 1.1.9Gemfile
RubyGemsrspec~> 3.3Gemfile
RubyGemsruby_memcheck—Gemfile
RubyGemsyard—Gemfile
RubyGemsjson—Gemfile
RubyGemsbenchmark-ips—Gemfile
All dependencies 9

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

RegistryPackageVersionRelation
RubyGemsbenchmark-ips—direct
RubyGemsjson—direct
RubyGemsrake—direct
RubyGemsrake-compiler—direct
RubyGemsrspec—direct
RubyGemsrubocop—direct
RubyGemsruby_memcheck—direct
RubyGemssimplecov—direct
RubyGemsyard—direct
Dependency advisories not assessed

Advisory matching could not run for this report: No resolved dependencies carried a version and a supported ecosystem

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.