Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-05 18:28 UTC

hausgold / grape-jwt-authentication

A reusable Grape JWT authentication concern

Ruby · MakefileMIT★ 33 stars⑂ 9 forkssince Nov 2017View on GitHub ↗
KindLibraryCommand-line toolhow this is determined

hausgold/grape-jwt-authentication holds a health index of 73 out of 100, placing it in the Good band. It scores highest on Engineering Quality (90/100) and lowest on Security (40/100). It was last updated 9 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

HAUSGOLDOrganization · verified domain
8 followers39 public repossince Sep 2016

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
RubyGemsgrape-jwt-authentication3.15.0-419 days ago

Metrics by category

Vitality

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

70Good · 21% of overall
How it's scored
28.8/36Push recencylast push 9 days ago
11.8/36Commit cadence17/52 weeks with commits
14.5/18Commit volume40 commits in the last year
3/10OpenSSF Scorecard: Maintained4 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 3
Inputs used
commits_last_year40
human_commit_share1
days_since_last_push9
active_weeks_last_year17
How it's scored
16.2/27Ships releases42 version tags (no GitHub releases)
36/36Release recencylatest release 9 days ago
27/27Release cadencea release every ~24.4 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count42
latest_release_tagv3.15.0
releases_from_tagsyes
days_since_latest_release9
mean_days_between_releases24.4
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?

56Moderate · 17% of overall
How it's scored
24.4/60Stars33 stars
7.5/25Forks9 forks
5.3/15Watchers10 watchers
Inputs used
forks9
stars33
watchers10
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (MIT)
0/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges2
has_contributingno
has_issue_templateno
has_code_of_conductyes
readme_badge_servicesbadge.fury.io, github.com
has_pull_request_templateno
How it's scored
59.1/80Total downloads486,349 downloads all-time across rubygems
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagesgrape-jwt-authentication
dependents
ecosystemsrubygems
total_downloads486,349
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?

65Good · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
6/22.5Commit distributiontop contributor authored 73% of commits
5.4/13.5Contributor breadth4 contributors
6/10OpenSSF Scorecard: Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
Inputs used
bus_factor1
contributors_sampled4
top_contributor_share0.732
How it's scored
28/42Issue resolution67% of issues closed
29.2/30PR acceptance39/40 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 0/30 approved changesets -- score normalized to 0
Inputs used
merged_prs39
open_issues1
closed_issues2
prs_merged_7d0
prs_decided_7d0
prs_merged_30d1
prs_decided_30d1
issue_closed_ratio0.667
closed_unmerged_prs1
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 backingorganization-owned
20/20Verified domain
6.9/25Owner reach8 followers of hausgold
23.7/25Track record39 public repos, account ~10 yr old
Inputs used
followers8
owner_typeOrganization
is_verifiedyes
owner_loginhausgold
public_repos39
account_age_days3,655

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable1 package(s) on rubygems
35/35Publish recencylatest publish 9 days ago
20/20Version history41 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesgrape-jwt-authentication
ecosystemsrubygems
any_deprecatedno
min_days_since_publish9

Engineering Quality

Are baseline engineering and documentation practices in place?

90Excellent · 19% of overall
How it's scored
24/24CI workflows2 workflow(s)
24/24Tests present
16/16Linter config.rubocop.yml
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests13 out of 13 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigyes
has_linter_configyes
has_precommit_configno

Documentation

90Excellent
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage sitehttps://rubygems.org/gems/grape-jwt-authentication
10/10Repository description
10/10Topics10 topics
0/10Wiki
Inputs used
topicsgrape, grape-api, concern, jwt, authentification, middleware, rack, oss, gem, ruby-gem
has_wikino
homepagehttps://rubygems.org/gems/grape-jwt-authentication
docs_sitehttps://rubygems.org/gems/grape-jwt-authentication
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

40Weak · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionno data
2.5/2.5CI-Tests13 out of 13 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0/7.5Code-ReviewFound 0/30 approved changesets -- score normalized to 0
1.5/2.5Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
10/10Dangerous-Workflowno dangerous workflow patterns detected
0/7.5Dependency-Update-Toolno update tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
2.2/7.5Maintained4 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 3
0/5Packagingno data
0/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0/5SASTSAST tool is not run on all commits -- score normalized to 0
0/5Security-Policysecurity policy file not detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate4
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.

45Weak · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
18.1/40Legible commit history34 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.34
agent_instruction_files
agent_instruction_max_bytes
How it's scored
18/18One-command bootstrapMakefile
22/22Automated tests
11/11Lint / format config.rubocop.yml
0/11Static type checking
10/10Reproducible environmentDockerfile
0/10Demonstrated agent practiceno agent-authored commits among the last 100
0/8Automated maintenanceno automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfiles
has_dockerfileyes
typed_languageno
bootstrap_filesMakefile
has_devcontainerno
has_linter_configyes
typecheck_configs
agent_commit_share0
toolchain_manifests
dependency_bot_commit_share0
How it's scored
0/45Type-checkable codeRuby without a type-check config
55/55Manageable file sizes0/16 source files over 60KB
Inputs used
primary_languageRuby
largest_source_bytes8,017
source_files_sampled16
oversized_source_files0

Key facts

33GitHub stars
4contributors
40commits, last 12 months
9days since last push
42releases
1bus factor
1open 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 ★ / 9 ⇿
0Stars
9Forks
8Releases

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.

0246810912019-042021-092024-01
Major 1Minor 3Patch 4

Each point covers 5 days.

OpenSSF Scorecard 4.0 / 10
4.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-05 18:28 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-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
0Code-ReviewFound 0/30 approved changesets -- score normalized to 0
6Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update 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
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 19
RegistryPackageVersion constraintManifest
RubyGemsappraisal~> 2.4Gemfile
RubyGemsbundler>= 2.6Gemfile
RubyGemscountless~> 2.2Gemfile
RubyGemsguard-rspec~> 4.7Gemfile
RubyGemsrack>= 3.0Gemfile
RubyGemsrack-test~> 2.0Gemfile
RubyGemsrackup>= 1.0Gemfile
RubyGemsrailties>= 8.1Gemfile
RubyGemsrake~> 13.0Gemfile
RubyGemsrspec~> 3.12Gemfile
RubyGemsrubocopGemfile
RubyGemsrubocop-railsGemfile
RubyGemsrubocop-rspecGemfile
RubyGemssimplecov>= 0.22Gemfile
RubyGemstimecop>= 0.9.6Gemfile
RubyGemsvcr~> 6.0Gemfile
RubyGemswebmock~> 3.18Gemfile
RubyGemsyard>= 0.9.28Gemfile
RubyGemsyard-activesupport-concern>= 0.0.1Gemfile
All dependencies 26

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

RegistryPackageVersionRelation
RubyGemsappraisaldirect
RubyGemsbundlerdirect
RubyGemscountlessdirect
RubyGemsguard-rspecdirect
RubyGemsrackdirect
RubyGemsrack-testdirect
RubyGemsrackupdirect
RubyGemsrailtiesdirect
RubyGemsrakedirect
RubyGemsrspecdirect
RubyGemsrubocopdirect
RubyGemsrubocop-railsdirect
RubyGemsrubocop-rspecdirect
RubyGemssimplecovdirect
RubyGemstimecopdirect
RubyGemsvcrdirect
RubyGemswebmockdirect
RubyGemsyarddirect
RubyGemsyard-activesupport-concerndirect
RubyGemsactivesupportindirect
RubyGemsgrapeindirect
RubyGemsjwtindirect
RubyGemskeylessindirect
RubyGemsloggerindirect
RubyGemsrecursive-open-structindirect
RubyGemszeitwerkindirect
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 statisticsRubyGems.