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

applicable weight 80%

user01/examples

Language: Go
branch master
imported from GitHub

Examples of code, configuration files etc. to be used with Yandex Cloud.

Open on SourceCraftDownload report (Markdown)snapshot 8 October 2026signal coverage 80%analysed 17 September 2026 at 18:59 UTC — part unavailable

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 practicessignal coverage 67%
5.5–13.8 / 25
partial
Project activity
8.3 / 25
scored
Securitywill appear with a member token
no data
CI/CDsignal coverage 50%
0–9.4 / 18.8
partial
Issues
3.6 / 18.8
scored
Code health
0–12.5 / 12.5
collection failed
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: tests directory, docs directory, Dockerfile, contributing guide, TODO/FIXME density
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
  • Contributions are spread across authors
  • A team works on the project (20 authors)
  • Commit messages are meaningful

What affected the score

Penalties

Documentation and best practices

  • −3
    README220 chars, no quickstart
  • −2
    license filemissing
  • −2
    dependency lockfilemissing
  • −2
    review policyno protection
  • −1
    branch protection policyno protection
  • −<1
    share of short commit messages — 2%

Project activity

  • −4
    last commit — 601 days
  • −4
    commits in the last year — 0 commits
  • −4
    weekly activity — 0 weeks
  • −4
    last releaseno releases or version tags

CI/CD

  • −9
    SourceCraft CI configurationmissing

Issues

  • −15
    age of open issues — 449 days1 issue

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 −2
    tests directorydata not collected
  • up to −2
    docs directorydata not collected
  • up to −2
    Dockerfiledata not collected
  • up to −1
    contributing guidedata not collected

CI/CD

  • up to −9
    CI runsdata not collected

Code health

  • up to −13
    TODO/FIXME densitydata not collected

What will raise the score

by strength of impact
  • Issues
    +15
    work through the stale open issuesage of open issues — 449 dayswhy: an outside contributor gets an answer, and their work is not lostevidence: the repository's issue list, snapshot of 8 October 2026
  • CI/CD
    +9
    add a SourceCraft CI configuration (.sourcecraft/ci.yaml); the service does not see external CISourceCraft CI configurationwhy: the build and the checks are reproducible for whoever takes the code
  • Activity
    +4
    make a commit soonlast commit — 601 dayswhy: the repository shows it is alive, not abandoned
  • commit more often+4
  • spread work across more weeks instead of bursts+4
  • publish a release or tag a version+4
  • add a quickstart section to the README+3
  • add a license file+2
  • add a dependency lockfile+2
  • set up a review policy+2
  • set up a branch protection policy+1
  • write meaningful commit messages+<1