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

applicable weight 80%

ra-simakov/minego

Language: Go
branch main
Open on SourceCraftDownload report (Markdown)snapshot 8 October 2026signal coverage 80%analysed 17 September 2026 at 18:51 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.7 / 25
scored
Project activity
16.6 / 25
scored
Securitywill appear with a member token
no data
CI/CDsignal coverage 60%
9.8–17.3 / 18.8
partial
Issues
10.9 / 18.8
scored
Code health
12.5 / 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
  • Almost no marked debt in the code
  • SourceCraft CI is configured
  • The README introduces the project
  • Commits span the whole year (58 commits)
  • Work goes on without long pauses (8 weeks)

What affected the score

Penalties

Documentation and best practices

  • −2
    license filemissing
  • −2
    tests directorymissing
  • −2
    docs directorymissing
  • −2
    Dockerfilemissing
  • −2
    dependency lockfilemissing
  • −2
    review policyno protection
  • −1
    contributing guidemissing
  • −1
    branch protection policyno protection
  • −1
    share of short commit messages — 54%

Project activity

  • −2
    top author's share of commits — 84%
  • −2
    last release — 210 days
  • −2
    unique authors — 2 authors
  • −2
    last commit — 172 days

CI/CD

  • −2
    CI configuration contents

Issues

  • −6
    age of open issues — 217 days17 issues
  • −2
    issue resolution time — 7 days17 issues

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
  • Issues
    +6
    work through the stale open issuesage of open issues — 217 dayswhy: an outside contributor gets an answer, and their work is not lostevidence: the repository's issue list, snapshot of 8 October 2026
  • Activity
    +2
    share the work with other contributorstop author's share of commits — 84%why: the work does not rest on a single person
  • Documentation
    +2
    add a license filelicense filewhy: the terms of use are stated, not guessed
  • 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
  • close issues faster+2
  • publish a release or tag a version+2
  • bring in a second maintainer+2
  • make a commit soon+2
  • run CI on pull requests, not only on pushes to the default branch+2
  • add a contributing guide+1
  • set up a branch protection policy+1
  • write meaningful commit messages+1