← all organisations

hmgcc / Overview

4 public repositories, 16.9k commits, 3 committers, 2011–2026.

Every public repository in github.com/hmgcc was mirror-cloned in full and mined from its git history rather than the GitHub API alone. This site reports what 4 repositories, 16.9k commits and 3 people actually did.

The estate at a glance

4
public repositories
3 are forks of other projects
4
not archived
0 archived (0% of the estate)
16.9k
commits analysed
across 4 repositories with history
3
distinct human committers
plus 0 automated identities
687.8 MB
of git data
full mirrors, every branch and tag
11
languages detected
36.5 MB of source
15
years of history
org created February 2011
0%
of commits are bots
dependency bots and CI identities

What stands out

Roughly 0% of the estate is archived.

0 of 4 repositories are read-only. That is not neglect so much as a decade and a half of deliberate turnover: GDS has consistently retired work rather than leaving it to rot in place. The live estate is the 4 repositories that remain, and only those are a fair basis for judging current practice.

Shape of the estate

Repository status

Archived repositories are read-only. GDS archives aggressively, which is healthier than the alternative but makes the raw repository count a poor measure of the live system.

Active: 1 (25.0%)25%ActiveActive fork: 3 (75.0%)75%Active fork
  • Active, own code
  • Active fork of a third party
  • Archived (read-only)

Repositories created each year

The 2017 peak coincides with the GaaP era - Notify, Pay, Registers - and a wave of departmental prototyping.

32.21.50.8024: 12425: 325

Year of last push

A decay curve. The 2026 spike is the live estate; everything left of it has stopped moving.

4321025: 425

Volume of work

Commits per year, from git history

Measured from the commits themselves across every branch and tag, not from GitHub's activity graph.

2.6k1.9k1.3k646.8013: 4221314: 2k1415: 2.6k1516: 2k1617: 1.5k1718: 7611819: 6401920: 5862021: 4712122: 7542223: 1.4k2324: 2.1k2425: 1.5k25

The same history, month by month

Monthly resolution shows the texture the yearly view flattens: the long climb to the mid-2010s peak, the plateau, and the bot-driven noise of the Dependabot era. The busiest single month was 2016-07 with 526 commits.

526394.5263131.50: 4: 107: 172: 103: 362014-01: 278: 330: 20: 13: 201: 23: 184: 133: 145: 438: 143: 912015-01: 130: 431: 226: 174: 382: 141: 251: 186: 242: 139: 241: 442016-01: 130: 123: 203: 31: 183: 442: 526: 97: 66: 85: 98: 612017-01: 291: 63: 102: 115: 59: 87: 195: 287: 139: 87: 53: 582018-01: 21: 33: 45: 61: 98: 123: 58: 25: 71: 138: 30: 582019-01: 152: 86: 31: 85: 32: 50: 62: 9: 20: 43: 33: 372020-01: 44: 21: 75: 63: 79: 100: 58: 35: 17: 29: 25: 402021-01: 55: 25: 35: 29: 74: 61: 49: 29: 37: 22: 9: 462022-01: 52: 32: 119: 53: 37: 52: 41: 35: 33: 35: 124: 1412023-01: 144: 156: 112: 111: 144: 85: 104: 122: 145: 104: 134: 862024-01: 122: 152: 171: 129: 177: 148: 179: 189: 223: 299: 173: 1722025-01: 303: 319: 236: 289: 169: 162: 51

Languages

Primary language, by repository count

GitHub's headline language per repository. Ruby is the house language of GOV.UK publishing; Python dominates the data and alerting estate.

PythonPython: 11MDXMDX: 11TypeScriptTypeScript: 11

What GDS built

GDS has never been one product. Repository names carry the programme they were built for, and those prefixes outlive the programmes themselves – which makes them the clearest surviving record of what the organisation worked on, and when it stopped.

Repositories per programme

Classified by naming convention. 'Other / experimental' is the long tail of prototypes, spikes and one-off tools.

Forked third-partyForked third-party: 33Other / experimentalOther / experimental: 11

GitHub topics, as set by GDS itself

An independent check on the classification above: topics are applied by hand, and 0 of 4 repositories (0%) carry at least one. The ranking closely tracks the name-derived programmes, which is reassuring for both.

Commits per year, by programme

The rise and fall of each programme, measured in actual commits rather than announcements.

2.6k1.9k1.3k646.80111213 - Forked third-party: 4221314 - Forked third-party: 2k1415 - Forked third-party: 2.6k1516 - Forked third-party: 2k1617 - Forked third-party: 1.5k1718 - Forked third-party: 7611819 - Forked third-party: 6401920 - Forked third-party: 5862021 - Forked third-party: 4712122 - Forked third-party: 7542223 - Forked third-party: 1.4k2324 - Forked third-party: 2.1k24 - Other / experimental: 42425 - Forked third-party: 1.5k25 - Other / experimental: 52526
  • Forked third-party
  • Other / experimental

Programme life-spans

The period covering the middle 98% of each programme's commits. Deliberately not first-to-last commit: Emergency Alerts was built from the Notify codebase and inherited a stray 2011 commit with it, which made both programmes appear to start a decade before they existed. Trimming the tails ignores inherited and vendored history and answers the question actually being asked – when was this being worked on.

201120132015201720192021202320252027Forked third-partyForked third-party: sustained activity 2013 to 2025, 3 repositories, 16.9k commitsOther / experimentalOther / experimental: sustained activity 2024 to 2025, 1 repositories, 9 commits