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

applicable weight 80%

spbu-coding-2025/4-trees

Language: Kotlin
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
13 / 25
scored
Project activity
16.9 / 25
scored
Securitywill appear with a member token
no data
CI/CDsignal coverage 60%
11.3–18.8 / 18.8
partial
Issues
14.7 / 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
  • A team works on the project (4 authors)
  • Commits span the whole year (21 commits)

What affected the score

Penalties

Documentation and best practices

  • −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 — 10%

Project activity

  • −4
    last releaseno releases or version tags
  • −2
    last commit — 179 days
  • −1
    weekly activity — 3 weeks
  • −1
    top author's share of commits — 57%
  • −<1
    commits in the last year — 21 commits

Issues

  • −4
    age of open issues — 108 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

CI/CD

  • up to −8
    CI runsdata not collected

What will raise the score

by strength of impact
  • Activity
    +4
    publish a release or tag a versionlast releasewhy: the build and the checks are reproducible for whoever takes the code
  • Issues
    +4
    work through the stale open issuesage of open issues — 108 dayswhy: an outside contributor gets an answer, and their work is not lostevidence: the repository's issue list, snapshot of 8 October 2026
  • Documentation
    +2
    write project documentationdocs directorywhy: a newcomer can tell how to run the project and where to look
  • containerize the project — add a Dockerfile+2
  • add a dependency lockfile+2
  • set up a review policy+2
  • make a commit soon+2
  • spread work across more weeks instead of bursts+1
  • add a contributing guide+1
  • set up a branch protection policy+1
  • share the work with other contributors+1
  • commit more often+<1
  • write meaningful commit messages+<1