Skip to the main content
The Repo Vitals mark: a pulse that ends in a commitREPO VITALS

applicable weight 65%

yandex-cloud-examples/serverless-gitlab-runner

Language: Go
branch main
Open on SourceCraftDownload report (Markdown)snapshot 8 October 2026signal coverage 65%analysed 17 September 2026 at 18:40 UTC — not all categories measured

What the 100 is made of

category weight
Documentation 20Activity 20Security 20CI/CD 15Issues 15Code health 10

The light segments — Security: will appear with a member token; Issues: the tracker is empty or not set up. The rest share their weight for now.

Six categories

earned / weight
Documentation and best practicessignal coverage 71%
15.8–24.6 / 30.8
partial
Project activity
12.7 / 30.8
scored
Securitywill appear with a member token
no data
CI/CDsignal coverage 60%
9.2–18.5 / 23.1
partial
Issuesthe tracker is empty or not set up
no data
Code health
15.4 / 15.4
scored
States:
scored
partial
no data
weight goes to the rest
collection failed
interval, not zero
Not measured: CI runs
closed by the platform
will become a group once access opens
Not measured: README
couldn't see it
the platform's window was truncated: a deep file or a recent version may have fallen outside it

Strengths

what's already done
  • Almost no marked debt in the code
  • SourceCraft CI is configured
  • The license file is in place
  • The build is described by a Dockerfile
  • Dependency versions are pinned

What affected the score

Penalties

Documentation and best practices

  • −3
    tests directorymissing
  • −3
    docs directorymissing
  • −<1
    share of short commit messages — 24%

Project activity

  • −5
    top author's share of commits — 100%
  • −5
    unique authors — 1 author
  • −3
    last release — 219 days
  • −2
    last commit — 195 days
  • −2
    weekly activity — 3 weeks
  • −1
    commits in the last year — 14 commits

CI/CD

  • −5
    CI configuration contents

Not measured — interval width

Not a penalty: the lower bound of the score counts the metric as zero, the upper bound as full

Documentation and best practices

  • up to −9
    READMEdata not collected

CI/CD

  • up to −9
    CI runsdata not collected

What will raise the score

by strength of impact
  • Activity
    +5
    share the work with other contributorstop author's share of commits — 100%why: the work does not rest on a single person
  • Activity
    +5
    bring in a second maintainerunique authors — 1 authorwhy: the work does not rest on a single person
  • CI/CD
    +5
    run CI on pull requests, not only on pushes to the default branchCI configuration contentswhy: a change is reviewed, and the history stays readableevidence: CI config .sourcecraft/ci.yaml, snapshot of 8 October 2026
  • write tests for the project+3
  • write project documentation+3
  • publish a release or tag a version+3
  • make a commit soon+2
  • spread work across more weeks instead of bursts+2
  • commit more often+1
  • write meaningful commit messages+<1