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

applicable weight 55%

gerasimovgrishagerasimov/day-07

branch main

ВАЖНО! Для успешного выполнения задания нужно убрать галочку под этим полем, чтобы получить все ветки. Задание опирается на разные ветки в репозитории.

Open on SourceCraftDownload report (Markdown)snapshot 8 October 2026signal coverage 55%analysed 17 September 2026 at 20:31 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; Code health. The rest share their weight for now.

Six categories

earned / weight
Documentation and best practices
8 / 36.4
scored
Project activity
18.6 / 36.4
scored
Securitywill appear with a member token
no data
CI/CDsignal coverage 60%
10.9–21.8 / 27.3
partial
Issuesthe tracker is empty or not set up
no data
Code health
no data
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
  • SourceCraft CI is configured
  • Contributions are spread across authors
  • Commit messages are meaningful

What affected the score

Penalties

Documentation and best practices

  • −4
    README733 chars, no quickstart
  • −3
    license filemissing
  • −3
    tests directorymissing
  • −3
    docs directorymissing
  • −3
    Dockerfilemissing
  • −3
    dependency lockfilemissing
  • −3
    review policyno protection
  • −2
    contributing guidemissing
  • −2
    branch protection policyno protection

Project activity

  • −6
    last releaseno releases or version tags
  • −5
    last commit — 287 days
  • −3
    commits in the last year — 3 commits
  • −3
    weekly activity — 2 weeks
  • −1
    unique authors — 3 authors

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

CI/CD

  • up to −11
    CI runsdata not collected

What will raise the score

by strength of impact
  • Activity
    +6
    publish a release or tag a versionlast releasewhy: the build and the checks are reproducible for whoever takes the code
  • 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
  • Activity
    +5
    make a commit soonlast commit — 287 dayswhy: the repository shows it is alive, not abandoned
  • add a quickstart section to the README+4
  • add a license file+3
  • write tests for the project+3
  • write project documentation+3
  • containerize the project — add a Dockerfile+3
  • add a dependency lockfile+3
  • set up a review policy+3
  • commit more often+3
  • spread work across more weeks instead of bursts+3
  • add a contributing guide+2
  • set up a branch protection policy+2
  • bring in a second maintainer+1