Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-11-21 20:08 UTC

wealthsimple-community / graphql-ruby-hive

GraphQL Hive integration for `graphql-ruby`.

RubyMIT★ 5 stars⑂ 0 forkssince Jul 2026View on GitHub ↗

wealthsimple-community/graphql-ruby-hive holds a health index of 71 out of 100, placing it in the Good band. It scores highest on Engineering Quality (76/100) and lowest on AI Readiness (40/100). It was last updated 8 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

4 followers2 public repossince Jun 2026

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
RubyGemsgraphql-hive0.6.5-2567 days ago

Metrics by category

Vitality

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

68Good · 21% of overall
How it's scored
28.8/36Push recency — last push 8 days ago
3.5/36Commit cadence — 5/52 weeks with commits
10.6/18Commit volume — 14 commits in the last year
3/10OpenSSF Scorecard: Maintained — 4 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 3
Inputs used
commits_last_year14
human_commit_share—
days_since_last_push8
active_weeks_last_year5

Release discipline

100Exceptional
How it's scored
27/27Ships releases — 3 releases published
36/36Release recency — latest release 67 days ago
27/27Release cadence — a release every ~17 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count3
latest_release_tagv0.6.5
releases_from_tagsno
days_since_latest_release67
mean_days_between_releases17
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
9.8/60Stars — 5 stars
0/25Forks — 0 forks
0/15Watchers — 2 watchers
Inputs used
forks0
stars5
watchers2
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

92Excellent
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (MIT)
18/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges2
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_servicesbadge.fury.io, github.com
has_pull_request_templateyes
How it's scored
53.8/80Total downloads — 150,921 downloads all-time across rubygems
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesgraphql-hive
dependents—
ecosystemsrubygems
total_downloads150,921
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?

57Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
7.5/22.5Commit distribution — top contributor authored 67% of commits
4.1/13.5Contributor breadth — 3 contributors
0/10OpenSSF Scorecard: Contributors — project has 0 contributing companies or organizations -- score normalized to 0
Inputs used
bus_factor1
contributors_sampled3
top_contributor_share0.667
How it's scored
0/42Issue resolution — no issues or no data
26/30PR acceptance — 13/15 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
12/15OpenSSF Scorecard: Code-Review — Found 5/6 approved changesets -- score normalized to 8
Inputs used
merged_prs13
open_issues0
closed_issues0
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio—
closed_unmerged_prs2
first_time_authors_30d0
first_time_prs_merged_30d0
first_time_prs_decided_30d0
Excluded from scoring (no data or not applicable): Issue resolution, Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain
5/25Owner reach — 4 followers of wealthsimple-community
4.3/25Track record — 2 public repos, account ~0 yr old
Inputs used
followers4
owner_typeOrganization
is_verifiedno
owner_loginwealthsimple-community
public_repos2
account_age_days145

Package maintenance

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

Engineering Quality

Are baseline engineering and documentation practices in place?

76Good · 19% of overall
How it's scored
24/24CI workflows — 4 workflow(s)
24/24Tests present
16/16Linter config — .rubocop.yml
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 13 out of 13 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 — https://docs.graphql-hive.com/specs/integrations
10/10Repository description
10/10Topics — 3 topics
0/10Wiki
Inputs used
topicsgraphql, graphql-hive, ruby
has_wikino
homepage—
docs_sitehttps://docs.graphql-hive.com/specs/integrations
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

69Good · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
4.5/7.5Branch-Protection — branch protection is not maximal on development and all release branches
2.5/2.5CI-Tests — 13 out of 13 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
6/7.5Code-Review — Found 5/6 approved changesets -- score normalized to 8
0/2.5Contributors — project has 0 contributing companies or organizations -- score normalized to 0
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
2.2/7.5Maintained — 4 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 3
0/5Packaging — no data
3.5/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 7
5/5SAST — SAST tool is run on all commits
5/5Security-Policy — security policy file detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
0/7.5Vulnerabilities — 11 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate6.1
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
advisories11
affected_packages3
assessed_packages59
unassessed_packages1
affected_by_severityhigh 1, moderate 2
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 59 resolved dependencies against OSV. 1 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.

40Weak · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
0/40Legible commit history — no data
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share—
agent_instruction_files—
agent_instruction_max_bytes—
Excluded from scoring (no data or not applicable): Legible commit history. Remaining weights renormalized.
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 data
8/8Automated maintenance — 6 of the last 14 commits are automated dependency updates
7/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 7
Inputs used
has_nixno
has_testsyes
lockfilesGemfile.lock
has_dockerfileno
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configyes
typecheck_configs—
agent_commit_share—
toolchain_manifests—
dependency_bot_commit_share0.429
Excluded from scoring (no data or not applicable): Demonstrated agent practice. Remaining weights renormalized.
How it's scored
0/45Type-checkable code — Ruby without a type-check config
55/55Manageable file sizes — 0/21 source files over 60KB
Inputs used
primary_languageRuby
largest_source_bytes14,752
source_files_sampled21
oversized_source_files0

Key facts

5GitHub stars
3contributors
14commits, last 12 months
8days since last push
3releases
1bus factor
0open issues
RubyGemspackage ecosystems

Data collection warnings

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

More detail

OpenSSF Scorecard 6.1 / 10
6.1aggregate

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-11-21 20:08 UTC

10Binary-Artifactsno binaries found in the repo
6Branch-Protectionbranch protection is not maximal on development and all release branches
10CI-Tests13 out of 13 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
8Code-ReviewFound 5/6 approved changesets -- score normalized to 8
0Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
3Maintained4 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 3
n/aPackagingpackaging workflow not detected
7Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 7
10SASTSAST tool is run on all commits
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities11 existing vulnerabilities detected
All dependencies 60

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

RegistryPackageVersionRelation
RubyGemsaddressable2.9.0indirect
RubyGemsast2.4.2indirect
RubyGemsbase640.3.0indirect
RubyGemsbigdecimal4.1.2indirect
RubyGemscgi0.5.2indirect
RubyGemscrack1.0.1indirect
RubyGemsdate3.5.1indirect
RubyGemsdebug1.11.1indirect
RubyGemsdiff-lcs1.6.2indirect
RubyGemserb4.0.4.1indirect
RubyGemsfiber-storage1.0.0indirect
RubyGemsgraphql—indirect
RubyGemsgraphql2.6.9indirect
RubyGemshashdiff1.2.1indirect
RubyGemsio-console0.9.2indirect
RubyGemsirb1.18.0indirect
RubyGemsjson2.7.2indirect
RubyGemslanguage_server-protocol3.17.0.3indirect
RubyGemslint_roller1.1.0indirect
RubyGemslogger1.7.0indirect
RubyGemsmustermann2.0.2indirect
RubyGemsostruct0.6.3indirect
RubyGemsparallel1.26.3indirect
RubyGemsparser3.3.5.0indirect
RubyGemspp0.6.4indirect
RubyGemsprettyprint0.2.0indirect
RubyGemsprism1.9.0indirect
RubyGemspsych5.5.0indirect
RubyGemspublic_suffix5.1.1indirect
RubyGemsracc1.8.1indirect
RubyGemsrack2.2.24indirect
RubyGemsrack-protection2.2.4indirect
RubyGemsrack-test2.2.0indirect
RubyGemsrainbow3.1.1indirect
RubyGemsrake13.4.2indirect
RubyGemsrdoc7.2.0indirect
RubyGemsregexp_parser2.9.2indirect
RubyGemsreline0.7.0indirect
RubyGemsrexml3.4.4indirect
RubyGemsrspec3.13.2indirect
RubyGemsrspec-core3.13.6indirect
RubyGemsrspec-expectations3.13.5indirect
RubyGemsrspec-mocks3.13.8indirect
RubyGemsrspec-support3.13.7indirect
RubyGemsrubocop1.65.1indirect
RubyGemsrubocop-ast1.32.3indirect
RubyGemsrubocop-performance1.21.1indirect
RubyGemsruby-progressbar1.13.0indirect
RubyGemsruby2_keywords0.0.5indirect
RubyGemssinatra2.2.4indirect
RubyGemsstandard1.40.1indirect
RubyGemsstandard-custom1.0.2indirect
RubyGemsstandard-performance1.4.0indirect
RubyGemsstandardrb1.0.1indirect
RubyGemsstringio3.2.0indirect
RubyGemstilt2.4.0indirect
RubyGemstsort0.2.0indirect
RubyGemsunicode-display_width2.6.0indirect
RubyGemsvcr6.4.0indirect
RubyGemswebmock3.26.2indirect
Dependency advisories 3

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

PackageVersionRelationSeverityAdvisoriesFixed in
rack2.2.24indirecthigh33.2.8
addressable2.9.0indirectmoderate62.9.1
sinatra2.2.4indirectmoderate24.2.0

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.