Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-11-15 21:47 UTC

govuk-once / govuk-mobile-android-app

GOV.UK Android mobile app

KotlinMIT★ 11 stars⑂ 1 forksince Apr 2024View on GitHub ↗
KindMobile applicationhow this is determined

govuk-once/govuk-mobile-android-app holds a health index of 80 out of 100, placing it in the Excellent band. It scores highest on Vitality (100/100) and lowest on Community & Adoption (39/100). It was last updated 2 days ago. 2 contributors account for most of its recent work.

80
overall / 100
Excellent

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.

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

Ownership

govuk-onceOrganization
14 followers35 public repossince Oct 2025

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

Metrics by category

Vitality

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

100Exceptional · 21% of overall

Development activity

100Exceptional
How it's scored
36/36Push recency — last push 2 days ago
36/36Commit cadence — 52/52 weeks with commits
18/18Commit volume — 842 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year842
human_commit_share1
days_since_last_push2
active_weeks_last_year52

Release discipline

100Exceptional
How it's scored
27/27Ships releases — 27 releases published
36/36Release recency — latest release 19 days ago
27/27Release cadence — a release every ~12.2 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count27
latest_release_tagv1.11
releases_from_tagsno
days_since_latest_release19
mean_days_between_releases12.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?

39Weak · 17% of overall
How it's scored
16.2/60Stars — 11 stars
0/25Forks — 1 forks
7.6/15Watchers — 24 watchers
Inputs used
forks1
stars11
watchers24
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
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges0
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services—
has_pull_request_templateyes

Sustainability & Governance

Will the project survive its people — bus factor, responsiveness, who backs it, and package upkeep?

54Moderate · 23% of overall
How it's scored
25.2/54Bus factor — 2 contributor(s) cover half of all commits
13.1/22.5Commit distribution — top contributor authored 42% of commits
13.5/13.5Contributor breadth — 11 contributors
3/10OpenSSF Scorecard: Contributors — project has 1 contributing companies or organizations -- score normalized to 3
Inputs used
bus_factor2
contributors_sampled11
top_contributor_share0.419
How it's scored
0/42Issue resolution — 0% of issues closed
27.9/30PR acceptance — 883/951 decided PRs merged
13/13Newcomer PR acceptance — 4/4 first-time contributors' PRs merged in 30d
15/15OpenSSF Scorecard: Code-Review — all changesets reviewed
Inputs used
merged_prs883
open_issues3
closed_issues0
prs_merged_7d21
prs_decided_7d21
prs_merged_30d55
prs_decided_30d57
issue_closed_ratio0
closed_unmerged_prs68
first_time_authors_30d2
first_time_prs_merged_30d4
first_time_prs_decided_30d4
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain
8.5/25Owner reach — 14 followers of govuk-once
13.4/25Track record — 35 public repos, account ~1 yr old
Inputs used
followers14
owner_typeOrganization
is_verifiedno
owner_logingovuk-once
public_repos35
account_age_days380

Engineering Quality

Are baseline engineering and documentation practices in place?

70Good · 19% of overall
How it's scored
24/24CI workflows — 4 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 16 out of 16 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigyes
has_linter_configno
has_precommit_configno
How it's scored
30/30README
25/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
0/10Topics
0/10Wiki
Inputs used
topics—
has_wikino
homepage—
docs_site—
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

75Good · 16% of overall
How it's scored
6.8/7.5Binary-Artifacts — binaries present in source code
3.8/7.5Branch-Protection — branch protection is not maximal on development and all release branches
2.5/2.5CI-Tests — 16 out of 16 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
7.5/7.5Code-Review — all changesets reviewed
0.8/2.5Contributors — project has 1 contributing companies or organizations -- score normalized to 3
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
7.5/7.5Maintained — 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
0/5Packaging — no data
5/5Pinned-Dependencies — all dependencies are pinned
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 — 67 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate6.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
advisories6
affected_packages1
assessed_packages102
unassessed_packages0
affected_by_severitymoderate 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 102 resolved dependencies against OSV. 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.

56Moderate · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
13.9/40Legible commit history — 26 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.26
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
12.6/18One-command bootstrap — analytics/build.gradle.kts, app/build.gradle.kts, build.gradle.kts (toolchain convention, no task runner)
22/22Automated tests
0/11Lint / format config
11/11Static type checking — Kotlin (statically typed)
10/10Reproducible environment — lockfile
0/10Demonstrated agent practice — no agent-authored commits among the last 100
5/8Automated maintenance — dependency automation configured, none observed in the sampled commits
10/10OpenSSF Scorecard: Pinned-Dependencies — all dependencies are pinned
Inputs used
has_nixno
has_testsyes
lockfilesGemfile.lock
has_dockerfileno
typed_languageyes
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configs—
agent_commit_share0
toolchain_manifestsanalytics/build.gradle.kts, app/build.gradle.kts, build.gradle.kts, buildSrc/build.gradle.kts, config/build.gradle.kts, data/build.gradle.kts, design/build.gradle.kts, feature/chat/build.gradle.kts, feature/dvla/build.gradle.kts, feature/home/build.gradle.kts, feature/local/build.gradle.kts, feature/messages/build.gradle.kts, feature/search/build.gradle.kts, feature/settings/build.gradle.kts, feature/topics/build.gradle.kts, feature/travelalerts/build.gradle.kts, feature/visited/build.gradle.kts, govkit/build.gradle.kts, notifications/build.gradle.kts
dependency_bot_commit_share0
How it's scored
45/45Type-checkable code — Kotlin (statically typed)
55/55Manageable file sizes — 0/731 source files over 60KB
Inputs used
primary_languageKotlin
largest_source_bytes50,648
source_files_sampled731
oversized_source_files0

Key facts

11GitHub stars
11contributors
842commits, last 12 months
2days since last push
27releases
2bus factor
3open issues
Maven, RubyGemspackage ecosystems

Data collection warnings

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

More detail

OpenSSF Scorecard 6.9 / 10
6.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-11-15 21:46 UTC

9Binary-Artifactsbinaries present in source code
5Branch-Protectionbranch protection is not maximal on development and all release branches
10CI-Tests16 out of 16 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
3Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
10Pinned-Dependenciesall dependencies are pinned
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
0Vulnerabilities67 existing vulnerabilities detected
Direct dependencies 1
RegistryPackageVersion constraintManifest
RubyGemsfastlane—Gemfile
All dependencies 102

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

RegistryPackageVersionRelation
RubyGemsfastlane2.240.1direct
RubyGemsabbrev0.1.2indirect
RubyGemsaddressable2.9.0indirect
RubyGemsartifactory3.0.17indirect
RubyGemsatomos0.1.3indirect
RubyGemsaws-eventstream1.4.0indirect
RubyGemsaws-partitions1.1287.0indirect
RubyGemsaws-sdk-core3.257.0indirect
RubyGemsaws-sdk-kms1.132.0indirect
RubyGemsaws-sdk-s31.232.1indirect
RubyGemsaws-sigv41.12.1indirect
RubyGemsbabosa1.0.4indirect
RubyGemsbase640.3.0indirect
RubyGemsbenchmark0.5.0indirect
RubyGemsbigdecimal4.1.3indirect
RubyGemsCFPropertyList3.0.8indirect
RubyGemscgi0.5.2indirect
RubyGemsclaide1.1.0indirect
RubyGemscolored1.2indirect
RubyGemscolored23.1.2indirect
RubyGemscommander4.6.0indirect
RubyGemscsv3.3.6indirect
RubyGemsdeclarative0.0.20indirect
RubyGemsdigest-crc0.7.0indirect
RubyGemsdomain_name0.6.20260907indirect
RubyGemsdotenv2.8.1indirect
RubyGemsemoji_regex3.2.3indirect
RubyGemserb6.0.7indirect
RubyGemsexcon1.7.1indirect
RubyGemsfaraday2.14.4indirect
RubyGemsfaraday-cookie_jar0.0.8indirect
RubyGemsfaraday-follow_redirects0.5.0indirect
RubyGemsfaraday-multipart1.2.0indirect
RubyGemsfaraday-net_http3.4.4indirect
RubyGemsfaraday-retry2.4.0indirect
RubyGemsfastimage2.4.1indirect
RubyGemsfastlane-sirp1.1.0indirect
RubyGemsgh_inspector1.1.3indirect
RubyGemsgoogle-apis-androidpublisher_v30.108.0indirect
RubyGemsgoogle-apis-core1.2.5indirect
RubyGemsgoogle-apis-iamcredentials_v10.28.0indirect
RubyGemsgoogle-apis-playcustomapp_v10.18.0indirect
RubyGemsgoogle-apis-storage_v10.67.0indirect
RubyGemsgoogle-cloud-core1.9.0indirect
RubyGemsgoogle-cloud-env2.3.1indirect
RubyGemsgoogle-cloud-errors1.7.0indirect
RubyGemsgoogle-cloud-storage1.62.0indirect
RubyGemsgoogle-logging-utils0.2.0indirect
RubyGemsgoogleauth1.17.4indirect
RubyGemshighline2.0.3indirect
RubyGemshttp-cookie1.1.6indirect
RubyGemsio-console0.9.4indirect
RubyGemsirb1.18.0indirect
RubyGemsjmespath1.6.2indirect
RubyGemsjson2.21.2indirect
RubyGemsjwt3.3.0indirect
RubyGemslogger1.7.0indirect
RubyGemsmini_magick4.13.2indirect
RubyGemsmini_mime1.1.5indirect
RubyGemsmulti_json1.21.2indirect
RubyGemsmultipart-post2.4.1indirect
RubyGemsmutex_m0.3.0indirect
RubyGemsnanaimo0.4.0indirect
RubyGemsnaturally2.3.0indirect
RubyGemsnet-http0.9.1indirect
RubyGemsnkf0.3.0indirect
RubyGemsoptparse0.8.1indirect
RubyGemsos1.1.4indirect
RubyGemsostruct0.6.3indirect
RubyGemsplist3.7.2indirect
RubyGemspp0.6.4indirect
RubyGemsprettyprint0.2.0indirect
RubyGemsprism1.9.0indirect
RubyGemspstore0.2.1indirect
RubyGemspublic_suffix7.0.5indirect
RubyGemsrake13.4.2indirect
RubyGemsrbs4.2.0indirect
RubyGemsrdoc8.0.0indirect
RubyGemsreline0.7.0indirect
RubyGemsrepresentable3.2.0indirect
RubyGemsretriable4.2.0indirect
RubyGemsrexml3.4.4indirect
RubyGemsrouge3.28.0indirect
RubyGemsrubyzip3.7.0indirect
RubyGemssecurity0.3.0indirect
RubyGemssignet0.22.0indirect
RubyGemssimctl1.6.10indirect
RubyGemsterminal-notifier2.0.0indirect
RubyGemsterminal-table4.0.0indirect
RubyGemstrailblazer-option0.1.2indirect
RubyGemstsort0.2.0indirect
RubyGemstty-cursor0.7.1indirect
RubyGemstty-screen0.8.2indirect
RubyGemstty-spinner0.9.3indirect
RubyGemsuber0.1.0indirect
RubyGemsunicode-display_width3.3.0indirect
RubyGemsunicode-emoji4.3.0indirect
RubyGemsuri1.1.1indirect
RubyGemsword_wrap1.0.0indirect
RubyGemsxcodeproj1.28.1indirect
RubyGemsxcpretty0.4.1indirect
RubyGemsxcpretty-travis-formatter1.0.1indirect
Dependency advisories 1

This repository publishes no package the index resolves, so its own dependency graph was assessed — 102 packages, which also include development and test pins that never ship: 1 carry known advisories, of which 0 are direct.

PackageVersionRelationSeverityAdvisoriesFixed in
addressable2.9.0indirectmoderate62.9.1

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.