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

applicable weight 80%

timoxa102928/health-mock-strong

Language: Go
branch main

Grading mock repo (high, medium security/docs), generated by scripts/mock-repos/full

Open on SourceCraftDownload report (Markdown)snapshot 8 October 2026signal coverage 80%analysed 27 September 2026 at 21:55 UTC — not all categories measured

What the 100 is made of

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

The light segment — Security: will appear with a member token, while the rest share its weight for now.

Six categories

earned / weight
Documentation and best practices
7.9 / 25
scored
Project activity
20.8 / 25
scored
Securitywill appear with a member token
no data
CI/CDsignal coverage 60%
7.5–15 / 18.8
partial
Issues
18.8 / 18.8
scored
Code health
7.1 / 12.5
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

Strengths

what's already done
  • Open issues do not pile up (11 days)
  • SourceCraft CI is configured
  • Issues are closed quickly (today)
  • Commits are fresh (13 days)
  • Commits span the whole year (152 commits)

What affected the score

Penalties

Documentation and best practices

  • −3
    README651 chars, no quickstart
  • −2
    tests directorymissing
  • −2
    docs directorymissing
  • −2
    Dockerfilemissing
  • −2
    dependency lockfilemissing
  • −2
    review policyno protection
  • −1
    branch protection policyno protection
  • −1
    share of short commit messages — 100%

Project activity

  • −4
    last releaseno releases or version tags

CI/CD

  • −4
    CI configuration contents

Code health

  • −5
    TODO/FIXME density

Not measured — interval width

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

CI/CD

  • up to −8
    CI runsdata not collected

What will raise the score

by strength of impact
  • Code health
    +5
    work through the TODO/FIXME marks in the codeTODO/FIXME densitywhy: the code stays workable: marked debt does not pile up
  • Activity
    +4
    publish a release or tag a versionlast releasewhy: the build and the checks are reproducible for whoever takes the code
  • CI/CD
    +4
    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
  • add a quickstart section to the README+3
  • write tests for the project+2
  • write project documentation+2
  • containerize the project — add a Dockerfile+2
  • add a dependency lockfile+2
  • set up a review policy+2
  • set up a branch protection policy+1
  • write meaningful commit messages+1