Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-12 19:27 UTC

jruby / jruby-rack

Rack for JRuby and Java appservers

Ruby · JavaMIT★ 405 stars⑂ 139 forkssince May 2008View on GitHub ↗

jruby/jruby-rack holds a health index of 86 out of 100, placing it in the Excellent band. It scores highest on Vitality (96/100) and lowest on Community & Adoption (59/100). It was last updated 2 days ago. 2 contributors account 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

JRuby TeamOrganization
62 followers78 public repossince Feb 2009

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
Mavenorg.jruby.rack:jruby-rack2.0.0-5112 days ago

Metrics by category

Vitality

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

96Exceptional · 21% of overall
How it's scored
36/36Push recency — last push 2 days ago
29.8/36Commit cadence — 43/52 weeks with commits
18/18Commit volume — 311 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year311
human_commit_share0.9
days_since_last_push2
active_weeks_last_year43

Release discipline

100Exceptional
How it's scored
27/27Ships releases — 18 releases published
36/36Release recency — latest release 12 days ago
27/27Release cadence — a release every ~45 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count18
latest_release_tagjruby-rack-2.0.0
releases_from_tagsno
days_since_latest_release12
mean_days_between_releases45
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?

59Moderate · 17% of overall
How it's scored
42.3/60Stars — 405 stars
17.8/25Forks — 139 forks
7.2/15Watchers — 21 watchers
Inputs used
forks139
stars405
watchers21
growth_stateorganic
growth_factor_pct100
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_badges5
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicesgithub.com, shields.io
has_pull_request_templateno

Sustainability & Governance

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

75Good · 23% of overall
How it's scored
25.2/54Bus factor — 2 contributor(s) cover half of all commits
13.9/22.5Commit distribution — top contributor authored 38% of commits
13.5/13.5Contributor breadth — 39 contributors
10/10OpenSSF Scorecard: Contributors — project has 27 contributing companies or organizations
Inputs used
bus_factor2
contributors_sampled39
top_contributor_share0.384
How it's scored
41.1/42Issue resolution — 98% of issues closed
20.9/30PR acceptance — 203/292 decided PRs merged
13/13Newcomer PR acceptance — 1/1 first-time contributors' PRs merged in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/19 approved changesets -- score normalized to 0
Inputs used
merged_prs203
open_issues4
closed_issues188
prs_merged_7d6
prs_decided_7d7
prs_merged_30d11
prs_decided_30d12
issue_closed_ratio0.979
closed_unmerged_prs89
first_time_authors_30d1
first_time_prs_merged_30d1
first_time_prs_decided_30d1
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain
12.9/25Owner reach — 62 followers of jruby
25/25Track record — 78 public repos, account ~17 yr old
Inputs used
followers62
owner_typeOrganization
is_verifiedno
owner_loginjruby
public_repos78
account_age_days6,414

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on maven
35/35Publish recency — latest publish 12 days ago
20/20Version history — 51 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesorg.jruby.rack:jruby-rack
ecosystemsmaven
any_deprecatedno
min_days_since_publish12

Engineering Quality

Are baseline engineering and documentation practices in place?

65Good · 19% of overall
How it's scored
24/24CI workflows — 1 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 4 out of 4 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno

Documentation

60Moderate
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics — 8 topics
10/10Wiki
Inputs used
topicsrack-application, jruby, servlets, tomcat, warbler, deployment, rack-environment, jruby-rack
has_wikiyes
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?

64Moderate · 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
2.5/2.5CI-Tests — 4 out of 4 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
0/7.5Code-Review — Found 0/19 approved changesets -- score normalized to 0
2.5/2.5Contributors — project has 27 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 — 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
0/5Packaging — no data
3/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 6
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_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate5.5
Excluded from scoring (no data or not applicable): 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
25/25Indirect dependencies free of known advisories — no indirect dependency carries a known advisory
0/40No advisories left outstanding — no advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages32
unassessed_packages0
affected_by_severitynone
direct_affected_packages0
Excluded from scoring (no data or not applicable): No advisories left outstanding. Remaining weights renormalized. Matched the maven:org.jruby.rack:jruby-rack@2.0.0 runtime dependency closure — what installing the published package pulls in — 32 packages. 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.

61Moderate · 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 — 83 of 90 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.922
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
12.6/18One-command bootstrap — pom.xml (toolchain convention, no task runner)
22/22Automated tests
0/11Lint / format config
0/11Static type checking
10/10Reproducible environment — lockfile
6/10Demonstrated agent practice — 3 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance — 10 of the last 100 commits are automated dependency updates
6/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 6
Inputs used
has_nixno
has_testsyes
lockfilesGemfile.lock
has_dockerfileno
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configs—
agent_commit_share0.03
toolchain_manifestspom.xml
dependency_bot_commit_share0.1
How it's scored
0/45Type-checkable code — Ruby without a type-check config
55/55Manageable file sizes — 0/217 source files over 60KB
Inputs used
primary_languageRuby
largest_source_bytes41,867
source_files_sampled217
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

405GitHub stars
39contributors
311commits, last 12 months
2days since last push
18releases
2bus factor
4open issues
Maven, RubyGemspackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • Star history carried forward from 2026-07-18: GitHub restricted the stargazers API to repository admins, so it can no longer be collected. The repository has 405 stars today.

More detail

Star and fork history 403 ★ / 139 ⇿
403Stars
139Forks
15Releases

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.

Star history is shown as collected on 2026-07-18. GitHub restricted the stargazers API to repository administrators in July 2026, so this series can no longer be extended; the current star total above remains live.

0100200300400500403130852008-052017-062026-07
Major 0Minor 0Patch 8

Each point covers 17 days.

OpenSSF Scorecard 5.5 / 10
5.5aggregate

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-12 19:27 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
10CI-Tests4 out of 4 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/19 approved changesets -- score normalized to 0
10Contributorsproject has 27 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
6Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 6
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 2
RegistryPackageVersion constraintManifest
RubyGemsrack—Gemfile
RubyGemsrack~> 2.2.24Gemfile
All dependencies 62

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

RegistryPackageVersionRelation
RubyGemsrack—direct
RubyGemsrack2.2.24direct
Mavencom.github.jnr:jffi1.3.15indirect
Mavencom.github.jnr:jnr-a64asm1.0.0indirect
Mavencom.github.jnr:jnr-constants0.10.4indirect
Mavencom.github.jnr:jnr-enxio0.32.20indirect
Mavencom.github.jnr:jnr-ffi2.2.19indirect
Mavencom.github.jnr:jnr-netdb1.2.0indirect
Mavencom.github.jnr:jnr-posix3.1.22indirect
Mavencom.github.jnr:jnr-unixsocket0.38.25indirect
Mavencom.github.jnr:jnr-x86asm1.0.2indirect
Mavencom.headius:backport91.13indirect
Mavencom.headius:invokebinder1.14indirect
Mavencom.headius:options1.6indirect
Mavencommons-logging:commons-logging1.4.0indirect
Mavenio.micrometer:micrometer-commons1.16.7indirect
Mavenio.micrometer:micrometer-observation1.16.7indirect
Mavenjakarta.el:jakarta.el-api6.0.1indirect
Mavenjakarta.servlet.jsp:jakarta.servlet.jsp-api3.0.0indirect
Mavenjakarta.servlet:jakarta.servlet-api5.0.0indirect
Mavenjoda-time:joda-time2.14.0indirect
Mavenme.qmx.jitescript:jitescript0.4.1indirect
Mavenorg.apache.logging.log4j:log4j-api2.26.1indirect
Mavenorg.apache.logging.log4j:log4j-core2.26.1indirect
Mavenorg.crac:crac1.5.0indirect
Mavenorg.jruby.jcodings:jcodings1.0.63indirect
Mavenorg.jruby.joni:joni2.2.6indirect
Mavenorg.jruby:dirgra0.5indirect
Mavenorg.jruby:jruby10.0.6.0indirect
Mavenorg.jruby:jruby-base10.0.6.0indirect
Mavenorg.jruby:jruby-stdlib10.0.6.0indirect
Mavenorg.jruby:jzlib1.1.5indirect
Mavenorg.jspecify:jspecify1.0.0indirect
Mavenorg.ow2.asm:asm9.7.1indirect
Mavenorg.ow2.asm:asm-analysis9.7.1indirect
Mavenorg.ow2.asm:asm-commons9.7.1indirect
Mavenorg.ow2.asm:asm-tree9.7.1indirect
Mavenorg.ow2.asm:asm-util9.7.1indirect
Mavenorg.slf4j:slf4j-api2.0.19indirect
Mavenorg.slf4j:slf4j-simple2.0.19indirect
Mavenorg.springframework:spring-beans7.0.9indirect
Mavenorg.springframework:spring-core7.0.9indirect
Mavenorg.springframework:spring-test7.0.9indirect
Mavenorg.springframework:spring-web7.0.9indirect
RubyGemsappraisal2.5.0indirect
RubyGemscamping—indirect
RubyGemsdiff-lcs1.6.2indirect
RubyGemsjruby-rack—indirect
RubyGemsjson—indirect
RubyGemslogger1.7.0indirect
RubyGemsrails—indirect
RubyGemsrake13.4.2indirect
RubyGemsrexml3.4.4indirect
RubyGemsrspec3.13.2indirect
RubyGemsrspec-core3.13.6indirect
RubyGemsrspec-expectations3.13.5indirect
RubyGemsrspec-mocks3.13.8indirect
RubyGemsrspec-support3.13.7indirect
RubyGemssinatra—indirect
RubyGemssprockets-rails—indirect
RubyGemsthor1.5.0indirect
RubyGemswarbler—indirect
Dependency advisories 0

Installing maven:org.jruby.rack:jruby-rack@2.0.0 pulls in 32 packages, direct and transitive: 0 carry known advisories, of which 0 are direct dependencies.

No known advisories affect the assessed dependencies.

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