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

nxt-insurance / nxt_support

Support through reusable Mixins and Helpers for Ruby on Rails Applications

RubyMIT★ 13 stars⑂ 1 forksince Sep 2019View on GitHub ↗
KindLibraryCommand-line toolhow this is determined

nxt-insurance/nxt_support holds a health index of 63 out of 100, placing it in the Moderate band. It scores highest on Security (66/100) and lowest on Community & Adoption (43/100). It was last updated 1 day ago. 2 contributors account for most of its recent work.

63
overall / 100
Moderate

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.

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

Ownership

Getsafe Digital GmbHOrganization · verified domain
22 followers26 public repossince Aug 2017

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
RubyGemsnxt_support0.7.0-2565 days ago

Metrics by category

Vitality

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

65Good · 21% of overall
How it's scored
36/36Push recency — last push 1 days ago
9.7/36Commit cadence — 14/52 weeks with commits
11.3/18Commit volume — 17 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_year17
human_commit_share0.56
days_since_last_push1
active_weeks_last_year14
How it's scored
16.2/27Ships releases — 29 version tags (no GitHub releases)
36/36Release recency — latest release 65 days ago
12.6/27Release cadence — a release every ~174.2 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count29
latest_release_tagv0.7.0
releases_from_tagsyes
days_since_latest_release65
mean_days_between_releases174.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?

43Weak · 17% of overall
How it's scored
17.5/60Stars — 13 stars
0/25Forks — 1 forks
5.6/15Watchers — 11 watchers
Inputs used
forks1
stars13
watchers11
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
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_badges1
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicescircleci.com
has_pull_request_templateno
How it's scored
53/80Total downloads — 127,454 downloads all-time across rubygems
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesnxt_support
dependents—
ecosystemsrubygems
total_downloads127,454
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?

63Moderate · 23% of overall
How it's scored
25.2/54Bus factor — 2 contributor(s) cover half of all commits
12/22.5Commit distribution — top contributor authored 47% of commits
13.5/13.5Contributor breadth — 10 contributors
6/10OpenSSF Scorecard: Contributors — project has 2 contributing companies or organizations -- score normalized to 6
Inputs used
bus_factor2
contributors_sampled10
top_contributor_share0.466
How it's scored
0/42Issue resolution — 0% of issues closed
13.8/30PR acceptance — 80/174 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
6/15OpenSSF Scorecard: Code-Review — Found 10/21 approved changesets -- score normalized to 4
Inputs used
merged_prs80
open_issues1
closed_issues0
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0
closed_unmerged_prs94
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
9.8/25Owner reach — 22 followers of nxt-insurance
22.4/25Track record — 26 public repos, account ~9 yr old
Inputs used
followers22
owner_typeOrganization
is_verifiedyes
owner_loginnxt-insurance
public_repos26
account_age_days3,391

Package maintenance

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

Engineering Quality

Are baseline engineering and documentation practices in place?

60Moderate · 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
10/20OpenSSF Scorecard: CI-Tests — 17 out of 30 merged PRs checked by a CI test -- score normalized to 5
Inputs used
has_ciyes
has_testsyes
has_editorconfigyes
has_linter_configno
has_precommit_configno

Documentation

55Moderate
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage site — https://rubygems.org/gems/nxt_support
10/10Repository description
0/10Topics
0/10Wiki
Inputs used
topics—
has_wikino
homepagehttps://rubygems.org/gems/nxt_support
docs_sitehttps://rubygems.org/gems/nxt_support
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

66Good · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
3/7.5Branch-Protection — branch protection is not maximal on development and all release branches
1.2/2.5CI-Tests — 17 out of 30 merged PRs checked by a CI test -- score normalized to 5
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
3/7.5Code-Review — Found 10/21 approved changesets -- score normalized to 4
1.5/2.5Contributors — project has 2 contributing companies or organizations -- score normalized to 6
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
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
7.5/7.5Token-Permissions — GitHub workflow tokens follow principle of least privilege
6.8/7.5Vulnerabilities — 1 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate5.7
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
advisories1
affected_packages1
assessed_packages33
unassessed_packages9
affected_by_severitylow 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 33 resolved dependencies against OSV. 9 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
15/15Machine-readable docs (llms.txt) — llms.txt served by the project website (https://docs.ruby-lang.org/llms.txt)
31.4/40Legible commit history — 33 of 56 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://docs.ruby-lang.org/llms.txt
legible_history_share0.589
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
0/18One-command bootstrap
22/22Automated tests
0/11Lint / format config
0/11Static type checking
10/10Reproducible environment — lockfile
2/10Demonstrated agent practice — 1 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance — 44 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.01
toolchain_manifests—
dependency_bot_commit_share0.44
How it's scored
0/45Type-checkable code — Ruby without a type-check config
55/55Manageable file sizes — 0/48 source files over 60KB
Inputs used
primary_languageRuby
largest_source_bytes10,814
source_files_sampled48
oversized_source_files0

Key facts

13GitHub stars
10contributors
17commits, last 12 months
1days since last push
29releases
2bus factor
1open issues
RubyGemspackage ecosystems

Data collection warnings

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

More detail

OpenSSF Scorecard 5.7 / 10
5.7aggregate

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-20 20:58 UTC

10Binary-Artifactsno binaries found in the repo
4Branch-Protectionbranch protection is not maximal on development and all release branches
5CI-Tests17 out of 30 merged PRs checked by a CI test -- score normalized to 5
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
4Code-ReviewFound 10/21 approved changesets -- score normalized to 4
6Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
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
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
10Token-PermissionsGitHub workflow tokens follow principle of least privilege
9Vulnerabilities1 existing vulnerabilities detected
All dependencies 42

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

RegistryPackageVersionRelation
RubyGemsactivemodel8.1.4.1indirect
RubyGemsactiverecord—indirect
RubyGemsactiverecord8.1.4.1indirect
RubyGemsactivesupport—indirect
RubyGemsactivesupport8.1.4.1indirect
RubyGemsbase640.3.0indirect
RubyGemsbigdecimal4.1.2indirect
RubyGemsbundler—indirect
RubyGemscoderay1.1.3indirect
RubyGemsconcurrent-ruby1.3.8indirect
RubyGemsconnection_pool3.0.2indirect
RubyGemsdiff-lcs1.6.2indirect
RubyGemsdrb2.2.3indirect
RubyGemsi18n1.15.2indirect
RubyGemsio-console0.8.2indirect
RubyGemsjson2.21.1indirect
RubyGemslogger1.7.0indirect
RubyGemsmethod_source1.1.0indirect
RubyGemsmini_portile22.8.9indirect
RubyGemsminitest6.0.6indirect
RubyGemsnxt_init—indirect
RubyGemsnxt_init0.1.5indirect
RubyGemsnxt_registry—indirect
RubyGemsnxt_registry0.3.10indirect
RubyGemsprism1.9.0indirect
RubyGemspry—indirect
RubyGemspry0.16.0indirect
RubyGemsrake—indirect
RubyGemsrake13.4.2indirect
RubyGemsreline0.6.3indirect
RubyGemsrspec—indirect
RubyGemsrspec3.13.2indirect
RubyGemsrspec-core3.13.6indirect
RubyGemsrspec-expectations3.13.5indirect
RubyGemsrspec-mocks3.13.8indirect
RubyGemsrspec-support3.13.7indirect
RubyGemssecurerandom0.4.1indirect
RubyGemssqlite3—indirect
RubyGemssqlite32.10.2indirect
RubyGemstimeout0.6.1indirect
RubyGemstzinfo2.0.6indirect
RubyGemsuri1.1.1indirect
Dependency advisories 1

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

PackageVersionRelationSeverityAdvisoriesFixed in
json2.21.1indirectlow12.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.