Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-08-28 03:09 UTC

realm / jazzy

Soulful docs for Swift & Objective-C

Ruby · JavaScriptMIT★ 7,379 stars⑂ 414 forkssince Jun 2014View on GitHub ↗

realm/jazzy holds a health index of 75 out of 100, placing it in the Good band. It scores highest on Community & Adoption (83/100) and lowest on Vitality (43/100). It was last updated 58 days ago. 2 contributors account for most of its recent work.

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

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

Ownership

RealmOrganization · verified domain
883 followers92 public repossince May 2014

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
RubyGemsjazzy0.15.4-81311 days ago

Metrics by category

Vitality

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

43Weak · 21% of overall
How it's scored
18/36Push recency — last push 58 days ago
3.5/36Commit cadence — 5/52 weeks with commits
9.4/18Commit volume — 10 commits in the last year
0/10OpenSSF Scorecard: Maintained — 1 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Inputs used
commits_last_year10
human_commit_share0.94
days_since_last_push58
active_weeks_last_year5
How it's scored
27/27Ships releases — 64 releases published
16.2/36Release recency — latest release 311 days ago
12.6/27Release cadence — a release every ~169.7 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count64
latest_release_tagv0.15.4
releases_from_tagsno
days_since_latest_release311
mean_days_between_releases169.7
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?

83Excellent · 17% of overall
How it's scored
60/60Stars — 7,379 stars
21.8/25Forks — 414 forks
12.2/15Watchers — 155 watchers
Inputs used
forks414
stars7,379
watchers155
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (MIT)
18/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges1
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_servicesgithub.com
has_pull_request_templateno
How it's scored
68.2/80Total downloads — 3,623,951 downloads all-time across rubygems
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesjazzy
dependents—
ecosystemsrubygems
total_downloads3,623,951
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?

79Good · 23% of overall
How it's scored
25.2/54Bus factor — 2 contributor(s) cover half of all commits
12.1/22.5Commit distribution — top contributor authored 46% of commits
13.5/13.5Contributor breadth — 62 contributors
10/10OpenSSF Scorecard: Contributors — project has 57 contributing companies or organizations
Inputs used
bus_factor2
contributors_sampled62
top_contributor_share0.463
How it's scored
38.7/42Issue resolution — 92% of issues closed
25/30PR acceptance — 425/511 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 2/27 approved changesets -- score normalized to 0
Inputs used
merged_prs425
open_issues72
closed_issues834
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.921
closed_unmerged_prs86
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
20/20Verified domain
21.2/25Owner reach — 883 followers of realm
25/25Track record — 92 public repos, account ~12 yr old
Inputs used
followers883
owner_typeOrganization
is_verifiedyes
owner_loginrealm
public_repos92
account_age_days4,489
How it's scored
25/25Published & resolvable — 1 package(s) on rubygems
26/35Publish recency — latest publish 311 days ago
20/20Version history — 81 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesjazzy
ecosystemsrubygems
any_deprecatedno
min_days_since_publish311

Engineering Quality

Are baseline engineering and documentation practices in place?

72Good · 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
6/20OpenSSF Scorecard: CI-Tests — 8 out of 22 merged PRs checked by a CI test -- score normalized to 3
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 — https://realm.io
10/10Repository description
10/10Topics — 5 topics
10/10Wiki
Inputs used
topicsswift, sourcekit, sourcekitten, ruby, xcode
has_wikiyes
homepagehttps://realm.io
docs_sitehttps://realm.io
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

51Moderate · 16% of overall
How it's scored
6.8/7.5Binary-Artifacts — binaries present in source code
0/7.5Branch-Protection — branch protection not enabled on development/release branches
0.8/2.5CI-Tests — 8 out of 22 merged PRs checked by a CI test -- score normalized to 3
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0/7.5Code-Review — Found 2/27 approved changesets -- score normalized to 0
2.5/2.5Contributors — project has 57 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/7.5Maintained — 1 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
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
6/7.5Vulnerabilities — 2 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate3.9
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
advisories2
affected_packages2
assessed_packages100
unassessed_packages13
affected_by_severitymoderate 1, low 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 100 resolved dependencies against OSV. 13 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.

46Weak · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
39.1/40Legible commit history — 69 of 94 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.734
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
10/10Reproducible environment — lockfile
0/10Demonstrated agent practice — no agent-authored commits among the last 100
8/8Automated maintenance — 6 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, package-lock.json
has_dockerfileno
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configyes
typecheck_configs—
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0.06
How it's scored
0/45Type-checkable code — Ruby without a type-check config
48/55Manageable file sizes — 6/47 source files over 60KB
Inputs used
primary_languageRuby
largest_source_bytes276,654
source_files_sampled47
oversized_source_files6

Key facts

7,379GitHub stars
62contributors
10commits, last 12 months
58days since last push
64releases
2bus factor
72open issues
npm, RubyGemspackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • Could not fetch npm package 'jazzy-js' from its registry

More detail

Star and fork history 0 ★ / 414 ⇿
0Stars
414Forks
64Releases

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.

010020030040050040792014-062020-072026-07
Major 0Minor 15Patch 49

Each point covers 12 days.

OpenSSF Scorecard 3.9 / 10
3.9aggregate

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-08-28 03:08 UTC

9Binary-Artifactsbinaries present in source code
0Branch-Protectionbranch protection not enabled on development/release branches
3CI-Tests8 out of 22 merged PRs checked by a CI test -- score normalized to 3
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 2/27 approved changesets -- score normalized to 0
10Contributorsproject has 57 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
0Maintained1 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
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
8Vulnerabilities2 existing vulnerabilities detected
Direct dependencies 4
RegistryPackageVersion constraintManifest
npmcorejs-typeahead^1.3.1js/package.json
npmjquery^3.7.1js/package.json
npmkatex^0.16.8js/package.json
npmlunr^2.3.9js/package.json
All dependencies 113

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

RegistryPackageVersionRelation
npmcorejs-typeahead1.3.4direct
npmjquery3.7.1direct
npmkatex0.16.25direct
npmlunr2.3.9direct
npmcommander8.3.0indirect
RubyGemsactivesupport—indirect
RubyGemsactivesupport7.2.3.1indirect
RubyGemsaddressable2.9.0indirect
RubyGemsalgoliasearch1.27.5indirect
RubyGemsast2.4.3indirect
RubyGemsatomos0.1.3indirect
RubyGemsbacon1.2.0indirect
RubyGemsbase640.3.0indirect
RubyGemsbenchmark0.5.0indirect
RubyGemsbigdecimal4.1.2indirect
RubyGemsbundler—indirect
RubyGemsCFPropertyList3.0.8indirect
RubyGemsclaide1.1.0indirect
RubyGemsclaide-plugins0.9.2indirect
RubyGemscocoapods—indirect
RubyGemscocoapods1.16.2indirect
RubyGemscocoapods-core1.16.2indirect
RubyGemscocoapods-deintegrate1.0.5indirect
RubyGemscocoapods-downloader2.1indirect
RubyGemscocoapods-plugins1.0.0indirect
RubyGemscocoapods-search1.0.1indirect
RubyGemscocoapods-trunk1.6.0indirect
RubyGemscocoapods-try1.2.0indirect
RubyGemscolored23.1.2indirect
RubyGemsconcurrent-ruby1.3.7indirect
RubyGemsconnection_pool3.0.2indirect
RubyGemscork0.3.0indirect
RubyGemscrack1.0.1indirect
RubyGemsdanger9.6.0indirect
RubyGemsdiffy3.4.4indirect
RubyGemsdrb2.2.3indirect
RubyGemsescape0.0.4indirect
RubyGemsethon0.18.0indirect
RubyGemsfaraday2.14.3indirect
RubyGemsfaraday-http-cache2.7.0indirect
RubyGemsfaraday-net_http3.4.4indirect
RubyGemsffi1.17.4indirect
RubyGemsfourflusher2.3.1indirect
RubyGemsfuzzy_match2.0.4indirect
RubyGemsgh_inspector1.1.3indirect
RubyGemsgit4.3.2indirect
RubyGemshashdiff1.2.1indirect
RubyGemshttpclient2.9.0indirect
RubyGemsi18n1.15.2indirect
RubyGemsjson2.20.0indirect
RubyGemskramdown2.5.2indirect
RubyGemskramdown-parser-gfm1.1.0indirect
RubyGemslanguage_server-protocol3.17.0.5indirect
RubyGemsliferaft0.0.6indirect
RubyGemslint_roller1.1.0indirect
RubyGemslogger—indirect
RubyGemslogger1.7.0indirect
RubyGemsmini_portile22.8.9indirect
RubyGemsminitest5.27.0indirect
RubyGemsmocha3.1.0indirect
RubyGemsmocha-on-bacon0.2.3indirect
RubyGemsmolinillo0.8.0indirect
RubyGemsmustache—indirect
RubyGemsmustache1.1.2indirect
RubyGemsmutex_m0.3.0indirect
RubyGemsnanaimo0.4.0indirect
RubyGemsnap1.1.0indirect
RubyGemsnet-http0.9.1indirect
RubyGemsnetrc0.11.0indirect
RubyGemsoctokit10.0.0indirect
RubyGemsopen4—indirect
RubyGemsopen41.3.4indirect
RubyGemsparallel2.1.0indirect
RubyGemsparser3.3.11.1indirect
RubyGemsprettybacon0.0.2indirect
RubyGemsprism1.9.0indirect
RubyGemsprocess_executer4.0.4indirect
RubyGemspstore0.2.1indirect
RubyGemspublic_suffix4.0.7indirect
RubyGemsracc1.8.1indirect
RubyGemsrainbow3.1.1indirect
RubyGemsrake—indirect
RubyGemsrake13.4.2indirect
RubyGemsrchardet1.10.2indirect
RubyGemsredcarpet—indirect
RubyGemsredcarpet3.6.1indirect
RubyGemsregexp_parser2.12.0indirect
RubyGemsrexml—indirect
RubyGemsrexml3.4.4indirect
RubyGemsrouge—indirect
RubyGemsrouge4.7.0indirect
RubyGemsrubocop1.88.0indirect
RubyGemsrubocop-ast1.49.1indirect
RubyGemsruby-macho2.5.1indirect
RubyGemsruby-progressbar1.13.0indirect
RubyGemsruby2_keywords0.0.5indirect
RubyGemssassc—indirect
RubyGemssassc2.4.0indirect
RubyGemssawyer0.9.3indirect
RubyGemssecurerandom0.4.1indirect
RubyGemssqlite3—indirect
RubyGemssqlite31.7.3indirect
RubyGemsterminal-table4.0.0indirect
RubyGemstrack_open_instances0.1.15indirect
RubyGemstyphoeus1.6.0indirect
RubyGemstzinfo2.0.6indirect
RubyGemsunicode-display_width3.2.0indirect
RubyGemsunicode-emoji4.2.0indirect
RubyGemsuri1.1.1indirect
RubyGemswebmock3.26.2indirect
RubyGemsxcinvoke—indirect
RubyGemsxcinvoke0.3.0indirect
RubyGemsxcodeproj1.27.0indirect
Dependency advisories 2

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

PackageVersionRelationSeverityAdvisoriesFixed in
sqlite31.7.3indirectmoderate12.9.5
json2.20.0indirectlow12.21.2

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.