Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-01 12:22 UTC

alphagov / govuk_app_config

Gem to configure GOV.UK Ruby applications

RubyMIT★ 11 stars⑂ 4 forkssince Aug 2017View on GitHub ↗
KindLibraryCommand-line toolhow this is determined

alphagov/govuk_app_config holds a health index of 94 out of 100, placing it in the Exceptional band. It scores highest on Vitality (89/100) and lowest on AI Readiness (49/100). It was last updated today. 6 contributors account for most of its recent work.

94
overall / 100
Exceptional

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.

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

Ownership

1,613 followers1,453 public repossince Feb 2011

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
RubyGemsgovuk_app_config9.25.2-2220 days ago

Metrics by category

Vitality

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

89Excellent · 21% of overall
How it's scored
36/36Push recencylast push 0 days ago
26.3/36Commit cadence38/52 weeks with commits
18/18Commit volume178 commits in the last year
10/10OpenSSF Scorecard: Maintained18 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year178
human_commit_share0.71
days_since_last_push0
active_weeks_last_year38
How it's scored
16.2/27Ships releases100 version tags (no GitHub releases)
36/36Release recencylatest release 0 days ago
27/27Release cadencea release every ~18.5 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count100
latest_release_tagv9.25.2
releases_from_tagsyes
days_since_latest_release0
mean_days_between_releases18.5
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?

57Moderate · 17% of overall
How it's scored
16.2/60Stars11 stars
4/25Forks4 forks
9.6/15Watchers55 watchers
Inputs used
forks4
stars11
watchers55
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
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges0
has_contributingno
has_issue_templateno
has_code_of_conductyes
readme_badge_services
has_pull_request_templateyes
How it's scored
62.2/80Total downloads965,032 downloads all-time across rubygems
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagesgovuk_app_config
dependents
ecosystemsrubygems
total_downloads965,032
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?

86Excellent · 23% of overall
How it's scored
48.6/54Bus factor6 contributor(s) cover half of all commits
20/22.5Commit distributiontop contributor authored 11% of commits
13.5/13.5Contributor breadth68 contributors
10/10OpenSSF Scorecard: Contributorsproject has 14 contributing companies or organizations
Inputs used
bus_factor6
contributors_sampled68
top_contributor_share0.11
How it's scored
30/42Issue resolution71% of issues closed
25.8/30PR acceptance527/612 decided PRs merged
6.5/13Newcomer PR acceptance1/2 first-time contributors' PRs merged in 30d
15/15OpenSSF Scorecard: Code-Reviewall changesets reviewed
Inputs used
merged_prs527
open_issues2
closed_issues5
prs_merged_7d1
prs_decided_7d2
prs_merged_30d1
prs_decided_30d2
issue_closed_ratio0.714
closed_unmerged_prs85
first_time_authors_30d1
first_time_prs_merged_30d1
first_time_prs_decided_30d2
How it's scored
30/30Ownership backingorganization-owned
0/20Verified domain
23.1/25Owner reach1,613 followers of alphagov
25/25Track record1,453 public repos, account ~15 yr old
Inputs used
followers1,613
owner_typeOrganization
is_verifiedno
owner_loginalphagov
public_repos1,453
account_age_days5,689

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable1 package(s) on rubygems
35/35Publish recencylatest publish 0 days ago
20/20Version history222 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesgovuk_app_config
ecosystemsrubygems
any_deprecatedno
min_days_since_publish0

Engineering Quality

Are baseline engineering and documentation practices in place?

86Excellent · 19% of overall
How it's scored
24/24CI workflows4 workflow(s)
24/24Tests present
16/16Linter config.rubocop.yml
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests15 out of 15 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

Documentation

90Excellent
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage sitehttps://rubygems.org/gems/govuk_app_config
10/10Repository description
10/10Topics1 topics
0/10Wiki
Inputs used
topicsgovuk
has_wikino
homepagehttps://rubygems.org/gems/govuk_app_config
docs_sitehttps://rubygems.org/gems/govuk_app_config
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

82Excellent · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
6/7.5Branch-Protectionbranch protection is not maximal on development and all release branches
2.5/2.5CI-Tests15 out of 15 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
7.5/7.5Code-Reviewall changesets reviewed
2.5/2.5Contributorsproject has 14 contributing companies or organizations
10/10Dangerous-Workflowno dangerous workflow patterns detected
7.5/7.5Dependency-Update-Toolupdate tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
7.5/7.5Maintained18 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
0/5Packagingno data
1/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 2
5/5SASTSAST tool is run on all commits
5/5Security-Policysecurity policy file 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_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate7.8
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 advisoriesno direct dependency carries a known advisory
0/25Indirect dependencies free of known advisoriestransitive set not separable from development and test dependencies in this scope
0/40No advisories left outstandingno advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages1
unassessed_packages21
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 1 resolved dependencies against OSV. 21 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 instructionsno CLAUDE.md / AGENTS.md / editor rules
15/15Machine-readable docs (llms.txt)llms.txt served by the project website (https://docs.sentry.io/llms.txt)
40/40Legible commit history56 of 71 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://docs.sentry.io/llms.txt
legible_history_share0.789
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
0/10Reproducible environment
0/10Demonstrated agent practiceno agent-authored commits among the last 100
8/8Automated maintenance29 of the last 100 commits are automated dependency updates
2/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 2
Inputs used
has_nixno
has_testsyes
lockfiles
has_dockerfileno
typed_languageno
bootstrap_files
has_devcontainerno
has_linter_configyes
typecheck_configs
agent_commit_share0
toolchain_manifests
dependency_bot_commit_share0.29
How it's scored
0/45Type-checkable codeRuby without a type-check config
55/55Manageable file sizes0/43 source files over 60KB
Inputs used
primary_languageRuby
largest_source_bytes9,710
source_files_sampled43
oversized_source_files0

Key facts

11GitHub stars
68contributors
178commits, last 12 months
0days since last push
100releases
6bus factor
2open issues
RubyGemspackage ecosystems

Data collection warnings

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

More detail

Star and fork history 0 ★ / 4 ⇿
0Stars
4Forks
99Releases

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.

1223344422019-082023-022026-07
Major 0Minor 23Patch 76

Each point covers 7 days.

OpenSSF Scorecard 7.8 / 10
7.8aggregate

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-01 12:22 UTC

10Binary-Artifactsno binaries found in the repo
8Branch-Protectionbranch protection is not maximal on development and all release branches
10CI-Tests15 out of 15 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
10Code-Reviewall changesets reviewed
10Contributorsproject has 14 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained18 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
2Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 2
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
10Vulnerabilities0 existing vulnerabilities detected
All dependencies 22

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

RegistryPackageVersionRelation
RubyGemsbyebugindirect
RubyGemsclimate_controlindirect
RubyGemsconnection_poolindirect
RubyGemslogstasherindirect
RubyGemsopentelemetry-exporter-otlpindirect
RubyGemsopentelemetry-instrumentation-allindirect
RubyGemsopentelemetry-sdkindirect
RubyGemsplekindirect
RubyGemsprometheus_exporterindirect
RubyGemspumaindirect
RubyGemsrack-proxyindirect
RubyGemsrack-testindirect
RubyGemsrailsindirect
RubyGemsrakeindirect
RubyGemsrspecindirect
RubyGemsrspec-itsindirect
RubyGemsrubocop-govuk5.2.1indirect
RubyGemssentry-railsindirect
RubyGemssentry-rubyindirect
RubyGemssimplecovindirect
RubyGemsstatsd-rubyindirect
RubyGemswebmockindirect
Dependency advisories 0

This repository publishes no package the index resolves, so its own dependency graph was assessed — 1 packages, which also include development and test pins that never ship: 0 carry known advisories, of which 0 are direct. 21 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 statisticsRubyGems.