Dashboard

What we count.

We look at the code repositories across Maersk’s GitHub. We only count repositories that are:

• Active
  Someone has changed the code in the last 12 months. Old and abandoned repositories are left out.
• Building a user interface
  They use a well-known tool for building screens, such as MDS, React, Angular or Tailwind. Repositories that don’t build screens (for example back-end services or data tools) are left out.

The share you see is the number of those repositories that use MDS.

How we segment.

Production-like repositories.

These look like real, maintained products rather than experiments. We call a repository production-like when all three are true:

• two or more people have worked on it in the last year,
• it has automated checks or has been deployed (see below),
• it is more than three months old.

This is our best guess from the signals we can see, not proof that a repository is live for real users.

Early-stage repositories.

Everything else. These tend to be prototypes, experiments and new projects: for example a single person working alone, a repository created in the last three months, or one with no automated checks. We split them in two:

• Early-stage, with CI
  It already has automated checks, but doesn’t yet meet the other tests (for example it has only one contributor, or is new).
• Early-stage, no CI
  It has no automated checks or deployments at all. These are the least mature, and fewest of them use MDS.

What is CI?

Continuous integration. It is a set of automated steps (such as running tests and building the app) that run every time someone changes the code. Having it usually means a team is looking after the code properly.

What is a deployment?

A record in GitHub saying “this version of the code was released to an environment”, such as a test or live environment. It is normally created automatically by a pipeline. It isn’t proof that real users are using the app (it could be a test environment), and a team that releases in another way might show none. That is why we look at several signals together.