Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-11-19 04:42 UTC

uktrade / github-standards

PythonNo license detected★ 1 star⑂ 4 forkssince Sep 2025View on GitHub ↗
KindCommand-line toolhow this is determined

uktrade/github-standards holds a health index of 80 out of 100, placing it in the Excellent band. It scores highest on Vitality (93/100) and lowest on Community & Adoption (26/100). It was last updated today. 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

164 followers43 public repossince Oct 2015

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?

93Exceptional · 21% of overall
How it's scored
36/36Push recency — last push 0 days ago
24.2/36Commit cadence — 35/52 weeks with commits
18/18Commit volume — 298 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_year298
human_commit_share0.92
days_since_last_push0
active_weeks_last_year35

Release discipline

100Exceptional
How it's scored
27/27Ships releases — 36 releases published
36/36Release recency — latest release 7 days ago
27/27Release cadence — a release every ~32.9 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count36
latest_release_tagv1.4.7
releases_from_tagsno
days_since_latest_release7
mean_days_between_releases32.9
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?

26At Risk · 17% of overall
How it's scored
0/60Stars — 1 stars
4/25Forks — 4 forks
0/15Watchers — 2 watchers
Inputs used
forks4
stars1
watchers2
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
0/22.5License — no license file detected
18/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseno
readme_badges0
has_contributingyes
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?

68Good · 23% of overall
How it's scored
25.2/54Bus factor — 2 contributor(s) cover half of all commits
11.9/22.5Commit distribution — top contributor authored 47% of commits
13.5/13.5Contributor breadth — 11 contributors
6/10OpenSSF Scorecard: Contributors — project has 2 contributing companies or organizations -- score normalized to 6
Inputs used
bus_factor2
contributors_sampled11
top_contributor_share0.472
How it's scored
29.4/42Issue resolution — 70% of issues closed
24.1/30PR acceptance — 211/263 decided PRs merged
11.1/13Newcomer PR acceptance — 6/7 first-time contributors' PRs merged in 30d
15/15OpenSSF Scorecard: Code-Review — all changesets reviewed
Inputs used
merged_prs211
open_issues3
closed_issues7
prs_merged_7d4
prs_decided_7d5
prs_merged_30d8
prs_decided_30d12
issue_closed_ratio0.7
closed_unmerged_prs52
first_time_authors_30d2
first_time_prs_merged_30d6
first_time_prs_decided_30d7
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain
15.9/25Owner reach — 164 followers of uktrade
24/25Track record — 43 public repos, account ~11 yr old
Inputs used
followers164
owner_typeOrganization
is_verifiedno
owner_loginuktrade
public_repos43
account_age_days4,054

Engineering Quality

Are baseline engineering and documentation practices in place?

68Good · 19% of overall
How it's scored
24/24CI workflows — 14 workflow(s)
24/24Tests present
16/16Linter config — pyproject.toml ([tool.ruff])
9.6/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 7 out of 7 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configyes

Documentation

30At Risk
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
0/10Repository description
0/10Topics
0/10Wiki
Inputs used
topics—
has_wikino
homepage—
docs_site—
has_readmeyes
has_docs_dirno
has_descriptionno

Security

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

84Excellent · 16% of overall

Security posture

80Excellent
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
3.8/7.5Branch-Protection — branch protection is not maximal on development and all release branches
2.5/2.5CI-Tests — 7 out of 7 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
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
0/2.5License — license file not detected
7.5/7.5Maintained — 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
5/5Packaging — packaging workflow detected
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
4.5/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate8
Excluded from scoring (no data or not applicable): 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
advisories0
affected_packages0
assessed_packages89
unassessed_packages0
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 89 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.

55Moderate · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
25.5/40Legible commit history — 44 of 92 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.478
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
18/18One-command bootstrap — Makefile
22/22Automated tests
11/11Lint / format config — pyproject.toml ([tool.ruff])
0/11Static type checking
10/10Reproducible environment — Dockerfile, lockfile
0/10Demonstrated agent practice — no agent-authored commits among the last 100
8/8Automated maintenance — 8 of the last 100 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
lockfilesuv.lock
has_dockerfileyes
typed_languageno
bootstrap_filesMakefile
has_devcontainerno
has_linter_configyes
typecheck_configs—
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0.08
How it's scored
0/45Type-checkable code — Python without a type-check config
55/55Manageable file sizes — 0/36 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes11,541
source_files_sampled36
oversized_source_files0

Key facts

1GitHub stars
11contributors
298commits, last 12 months
0days since last push
36releases
2bus factor
3open issues
PyPIpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • Could not fetch pypi package 'github-standards' from its registry

More detail

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

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.

1223344412025-102026-052026-11
Major 1Minor 4Patch 21
OpenSSF Scorecard 8.0 / 10
8.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-11-19 04:42 UTC

10Binary-Artifactsno binaries found in the repo
5Branch-Protectionbranch protection is not maximal on development and all release branches
10CI-Tests7 out of 7 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
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
0Licenselicense file not detected
10Maintained30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
10Packagingpackaging workflow 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
6Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 10
RegistryPackageVersion constraintManifest
PyPIpresidio-analyzer>=2.2.360pyproject.toml
PyPIproxy-py>=2.4.10pyproject.toml
PyPIpyyaml>=6.0.3pyproject.toml
PyPIen_core_web_sm@ https://github.com/explosion/spacy-models/releases/download/en_core_web_sm-3.8.0/en_core_web_sm-3.8.0-py3-none-any.whlpyproject.toml
PyPIgitpython>=3.1.59pyproject.toml
PyPIprettytable>=3.17.0pyproject.toml
PyPIasyncio>=4.0.0pyproject.toml
PyPIanyio>=4.13.0pyproject.toml
PyPIaiohttp>=3.13.2pyproject.toml
PyPImultidict==6.9.1pyproject.toml
All dependencies 89

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

RegistryPackageVersionRelation
PyPIaiohttp3.14.5direct
PyPIanyio4.16.0direct
PyPIasyncio4.0.0direct
PyPIen-core-web-sm3.8.0direct
PyPIgitpython3.2.1direct
PyPImultidict6.9.1direct
PyPIpresidio-analyzer2.2.366direct
PyPIprettytable3.18.0direct
PyPIproxy-py2.4.10direct
PyPIpyyaml6.0.3direct
PyPIaiohappyeyeballs2.7.1indirect
PyPIaiosignal1.4.0indirect
PyPIannotated-doc0.0.5indirect
PyPIannotated-types0.8.0indirect
PyPIattrs26.1.0indirect
PyPIblis1.3.4indirect
PyPIcatalogue2.0.10indirect
PyPIcertifi2026.10.23indirect
PyPIcfgv3.5.0indirect
PyPIcharset-normalizer3.5.2indirect
PyPIclick8.5.1indirect
PyPIcloudpathlib0.26.0indirect
PyPIcolorama0.4.6indirect
PyPIconfection1.3.4indirect
PyPIcoverage7.17.2indirect
PyPIcymem2.0.16indirect
PyPIdistlib0.4.4indirect
PyPIfilelock4.2.10indirect
PyPIfrozenlist1.8.0indirect
PyPIgitdb4.0.12indirect
PyPIgithub-standards1.4.7indirect
PyPIh110.16.0indirect
PyPIhttpcore1.0.9indirect
PyPIhttpx0.28.1indirect
PyPIidentify2.6.20indirect
PyPIidna3.20indirect
PyPIiniconfig2.3.1indirect
PyPIjinja23.1.6indirect
PyPImarkdown-it-py4.2.0indirect
PyPImarkupsafe3.0.4indirect
PyPImdurl0.1.2indirect
PyPImurmurhash1.0.16indirect
PyPInodeenv1.12.0indirect
PyPInumpy2.4.6indirect
PyPIpackaging26.3indirect
PyPIphonenumbers9.0.43indirect
PyPIplatformdirs4.14.5indirect
PyPIpluggy1.7.0indirect
PyPIpre-commit4.7.0indirect
PyPIpreshed3.0.13indirect
PyPIpropcache0.5.4indirect
PyPIpydantic2.14.3indirect
PyPIpydantic-core2.50.4indirect
PyPIpygments2.21.0indirect
PyPIpytest9.2.0indirect
PyPIpytest-aiohttp1.1.1indirect
PyPIpytest-asyncio1.4.1.post1indirect
PyPIpytest-cov7.1.0indirect
PyPIpytest-subprocess1.6.0indirect
PyPIpython-discovery1.9.5indirect
PyPIregex2026.11.9indirect
PyPIrequests2.34.2indirect
PyPIrequests-file3.0.1indirect
PyPIrequests-mock1.12.1indirect
PyPIrich15.0.0indirect
PyPIruff0.17.4indirect
PyPIsetuptools84.2.1indirect
PyPIsetuptools-scm10.3.4indirect
PyPIshellingham1.5.4indirect
PyPIsmart-open9.0.3indirect
PyPIsmmap5.0.3indirect
PyPIspacy3.8.18indirect
PyPIspacy-legacy3.0.12indirect
PyPIspacy-loggers1.0.5indirect
PyPIsrsly2.5.6indirect
PyPIthinc8.3.14indirect
PyPItldextract5.4.0indirect
PyPItqdm4.70.1indirect
PyPItyper0.29.0indirect
PyPItyping-extensions4.16.0indirect
PyPItyping-inspection0.4.5indirect
PyPIurllib32.8.0indirect
PyPIvcs-versioning2.6.0indirect
PyPIvirtualenv21.15.6indirect
PyPIwasabi1.1.3indirect
PyPIwcwidth0.9.4indirect
PyPIweasel1.0.1indirect
PyPIwrapt2.5.2indirect
PyPIyarl1.25.1indirect
Dependency advisories 0

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

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