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

jruby / warbler

Warbler chirpily constructs .war files of your Ruby applications.

Ruby · JavaMIT★ 900 stars⑂ 207 forkssince Mar 2008View on GitHub ↗
KindLibraryCommand-line toolhow this is determined

jruby/warbler holds a health index of 86 out of 100, placing it in the Excellent band. It scores highest on Vitality (86/100) and lowest on AI Readiness (49/100). It was last updated 1 day 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
RubyGemswarbler2.1.2-5613 days ago

Metrics by category

Vitality

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

86Excellent · 21% of overall
How it's scored
36/36Push recency — last push 1 days ago
24.2/36Commit cadence — 35/52 weeks with commits
18/18Commit volume — 248 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_year248
human_commit_share0.83
days_since_last_push1
active_weeks_last_year35
How it's scored
27/27Ships releases — 3 releases published
36/36Release recency — latest release 13 days ago
12.6/27Release cadence — a release every ~159.2 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count3
latest_release_tagv2.1.2
releases_from_tagsno
days_since_latest_release13
mean_days_between_releases159.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?

69Good · 17% of overall
How it's scored
47.9/60Stars — 900 stars
19.3/25Forks — 207 forks
7.7/15Watchers — 25 watchers
Inputs used
forks207
stars900
watchers25
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_badges—
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services—
has_pull_request_templateno
How it's scored
68.3/80Total downloads — 3,753,684 downloads all-time across rubygems
0/20Registry dependents — not reported by this ecosystem
Inputs used
packageswarbler
dependents—
ecosystemsrubygems
total_downloads3,753,684
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?

72Good · 23% of overall
How it's scored
25.2/54Bus factor — 2 contributor(s) cover half of all commits
15.9/22.5Commit distribution — top contributor authored 29% of commits
13.5/13.5Contributor breadth — 68 contributors
10/10OpenSSF Scorecard: Contributors — project has 58 contributing companies or organizations
Inputs used
bus_factor2
contributors_sampled68
top_contributor_share0.293
How it's scored
39.5/42Issue resolution — 94% of issues closed
23/30PR acceptance — 215/281 decided PRs merged
0/13Newcomer PR acceptance — 0/2 first-time contributors' PRs merged in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/16 approved changesets -- score normalized to 0
Inputs used
merged_prs215
open_issues23
closed_issues360
prs_merged_7d0
prs_decided_7d0
prs_merged_30d6
prs_decided_30d10
issue_closed_ratio0.94
closed_unmerged_prs66
first_time_authors_30d2
first_time_prs_merged_30d0
first_time_prs_decided_30d2
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 rubygems
35/35Publish recency — latest publish 13 days ago
20/20Version history — 56 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packageswarbler
ecosystemsrubygems
any_deprecatedno
min_days_since_publish13

Engineering Quality

Are baseline engineering and documentation practices in place?

74Good · 19% of overall
How it's scored
24/24CI workflows — 1 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 9 out of 9 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigyes
has_linter_configno
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage site — https://www.rubydoc.info/gems/warbler/2.1.2
10/10Repository description
10/10Topics — 6 topics
10/10Wiki
Inputs used
topicsjruby, war, servlet, packaging, ruby-on-rails, tomcat
has_wikiyes
homepage—
docs_sitehttps://www.rubydoc.info/gems/warbler/2.1.2
has_readmeyes
has_docs_dirno
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
6/7.5Binary-Artifacts — binaries present in source code
0/7.5Branch-Protection — branch protection not enabled on development/release branches
2.5/2.5CI-Tests — 9 out of 9 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/16 approved changesets -- score normalized to 0
2.5/2.5Contributors — project has 58 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
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_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate5
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
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
advisories0
affected_packages0
assessed_packages81
unassessed_packages23
affected_by_severitynone
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 81 resolved dependencies against OSV. 23 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.

49Weak · 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 83 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share1
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
12.6/18One-command bootstrap — ext/pom.xml, integration/pom.xml, integration/rails7_test/pom.xml (toolchain convention, no task runner)
22/22Automated tests
0/11Lint / format config
0/11Static type checking
10/10Reproducible environment — lockfile
0/10Demonstrated agent practice — no agent-authored commits among the last 100
8/8Automated maintenance — 17 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
lockfilesGemfile.lock
has_dockerfileno
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configs—
agent_commit_share0
toolchain_manifestsext/pom.xml, integration/pom.xml, integration/rails7_test/pom.xml, integration/runnable_test/pom.xml, integration/runnable_w_bundler_test/pom.xml, integration/simple_rack_test/pom.xml, pom.xml
dependency_bot_commit_share0.17
How it's scored
0/45Type-checkable code — Ruby without a type-check config
55/55Manageable file sizes — 0/95 source files over 60KB
Inputs used
primary_languageRuby
largest_source_bytes35,122
source_files_sampled95
oversized_source_files0

Key facts

900GitHub stars
68contributors
248commits, last 12 months
1days since last push
3releases
2bus factor
23open 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-06-28: GitHub restricted the stargazers API to repository admins, so it can no longer be collected. The repository has 900 stars today.
  • Could not fetch maven package 'org.jruby.warbler:warbler-jar' from its registry

More detail

Star and fork history 897 ★ / 207 ⇿
897Stars
207Forks
1Releases

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-06-28. 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.

02004006008001,000897198332008-032017-042026-06
Major 0Minor 1Patch 0

Each point covers 17 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-09-12 19:22 UTC

8Binary-Artifactsbinaries present in source code
0Branch-Protectionbranch protection not enabled on development/release branches
10CI-Tests9 out of 9 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/16 approved changesets -- score normalized to 0
10Contributorsproject has 58 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
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
All dependencies 104

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

RegistryPackageVersionRelation
Mavenorg.apache.maven.plugins:maven-clean-plugin—indirect
Mavenorg.apache.maven.plugins:maven-clean-plugin3.5.0indirect
Mavenorg.apache.maven.plugins:maven-compiler-plugin3.16.0indirect
Mavenorg.apache.maven.plugins:maven-enforcer-plugin3.6.3indirect
Mavenorg.apache.maven.plugins:maven-failsafe-plugin—indirect
Mavenorg.apache.maven.plugins:maven-failsafe-plugin3.6.0indirect
Mavenorg.apache.maven.plugins:maven-install-plugin3.1.4indirect
Mavenorg.apache.maven.plugins:maven-invoker-plugin—indirect
Mavenorg.apache.maven.plugins:maven-invoker-plugin3.10.1indirect
Mavenorg.apache.maven.plugins:maven-jar-plugin—indirect
Mavenorg.apache.maven.plugins:maven-jar-plugin3.5.1indirect
Mavenorg.apache.maven.plugins:maven-resources-plugin3.5.0indirect
Mavenorg.apache.maven.plugins:maven-surefire-plugin3.6.0indirect
Mavenorg.codehaus.mojo:exec-maven-plugin—indirect
Mavenorg.codehaus.mojo:exec-maven-plugin3.6.3indirect
Mavenorg.jruby.maven:jruby-maven-plugin—indirect
Mavenorg.jruby.maven:jruby-maven-plugin3.0.6indirect
Mavenorg.jruby:jruby—indirect
Mavenorg.junit.jupiter:junit-jupiter6.1.3indirect
RubyGemsactioncable7.2.3.2indirect
RubyGemsactionmailbox7.2.3.2indirect
RubyGemsactionmailer7.2.3.2indirect
RubyGemsactionpack7.2.3.2indirect
RubyGemsactiontext7.2.3.2indirect
RubyGemsactionview7.2.3.2indirect
RubyGemsactivejob7.2.3.2indirect
RubyGemsactivemodel7.2.3.2indirect
RubyGemsactiverecord7.2.3.2indirect
RubyGemsactiverecord-jdbc-adapter72.1indirect
RubyGemsactiverecord-jdbcpostgresql-adapter72.1indirect
RubyGemsactiverecord-jdbcsqlite3-adapter—indirect
RubyGemsactivestorage7.2.3.2indirect
RubyGemsactivesupport7.2.3.2indirect
RubyGemsbase640.3.0indirect
RubyGemsbenchmark0.5.0indirect
RubyGemsbigdecimal4.1.2indirect
RubyGemsbuilder3.3.0indirect
RubyGemscgi0.5.2indirect
RubyGemsconcurrent-ruby1.3.8indirect
RubyGemsconnection_pool3.0.2indirect
RubyGemscrass1.0.7indirect
RubyGemsdate3.5.1indirect
RubyGemsdrb—indirect
RubyGemsdrb2.2.3indirect
RubyGemserb4.0.4.1indirect
RubyGemserubi1.13.1indirect
RubyGemsglobalid1.4.0indirect
RubyGemshoe—indirect
RubyGemsi18n1.15.2indirect
RubyGemsio-console0.8.1indirect
RubyGemsirb1.15.2indirect
RubyGemsjar-dependencies0.5.5indirect
RubyGemsjbundler—indirect
RubyGemsjdbc-postgres42.7.8indirect
RubyGemsjruby-jars—indirect
RubyGemsjruby-rack—indirect
RubyGemsjson—indirect
RubyGemslogger1.7.0indirect
RubyGemsloofah2.25.2indirect
RubyGemsmail2.9.1indirect
RubyGemsmarcel1.2.1indirect
RubyGemsmini_mime1.1.5indirect
RubyGemsminitest—indirect
RubyGemsminitest5.27.0indirect
RubyGemsnet-imap0.6.6indirect
RubyGemsnet-pop0.1.2indirect
RubyGemsnet-protocol0.3.0indirect
RubyGemsnet-smtp0.5.1indirect
RubyGemsnio4r2.7.4indirect
RubyGemsnokogiri1.19.4indirect
RubyGemsostruct—indirect
RubyGemspp0.6.3indirect
RubyGemsprettyprint0.2.0indirect
RubyGemspsych5.2.6indirect
RubyGemsracc1.8.1indirect
RubyGemsrack—indirect
RubyGemsrack3.2.6indirect
RubyGemsrack-session2.1.2indirect
RubyGemsrack-test2.2.0indirect
RubyGemsrackup2.2.1indirect
RubyGemsrails—indirect
RubyGemsrails7.2.3.2indirect
RubyGemsrails-dom-testing2.3.0indirect
RubyGemsrails-html-sanitizer1.7.1indirect
RubyGemsrailties7.2.3.2indirect
RubyGemsrake—indirect
RubyGemsrake13.3.0indirect
RubyGemsrake13.4.2indirect
RubyGemsrdoc—indirect
RubyGemsrdoc6.15.0indirect
RubyGemsreline0.6.2indirect
RubyGemsrexml—indirect
RubyGemsrspec—indirect
RubyGemsrubyzip—indirect
RubyGemssecurerandom0.4.1indirect
RubyGemsstringio3.2.0indirect
RubyGemsthor1.4.0indirect
RubyGemstimeout0.6.1indirect
RubyGemstsort0.2.0indirect
RubyGemstzinfo2.0.6indirect
RubyGemsuseragent0.16.11indirect
RubyGemswebsocket-driver0.8.2indirect
RubyGemswebsocket-extensions0.1.5indirect
RubyGemszeitwerk2.6.18indirect
Dependency advisories 0

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

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