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

applicable weight 70%

testkek18-4/fvf

branch main

вфвфв

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

Six categories

earned / weight
Documentation and best practices
2.6 / 28.6
scored
Project activity
5.4 / 28.6
scored
Securitywill appear with a member token
no data
CI/CDsignal coverage 50%
0–10.7 / 21.4
partial
Issues
6.3 / 21.4
scored
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

No metric has a full score yet

What affected the score

Penalties

Documentation and best practices

  • −6
    README13 chars, no quickstart
  • −3
    license filemissing
  • −3
    tests directorymissing
  • −3
    docs directorymissing
  • −3
    Dockerfilemissing
  • −3
    dependency lockfilemissing
  • −3
    review policyno protection
  • −1
    contributing guidemissing
  • −1
    branch protection policyno protection
  • −1
    share of short commit messages — 91%

Project activity

  • −5
    last commit — 400 days
  • −5
    commits in the last year — 0 commits
  • −5
    weekly activity — 0 weeks
  • −5
    last releaseno releases or version tags
  • −2
    unique authors — 2 authors
  • −2
    top author's share of commits — 73%

CI/CD

  • −11
    SourceCraft CI configurationmissing

Issues

  • −15
    age of open issues — 390 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 −11
    CI runsdata not collected

What will raise the score

by strength of impact
  • Issues
    +15
    work through the stale open issuesage of open issues — 390 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
    +11
    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
  • Documentation
    +6
    add a quickstart section to the READMEREADMEwhy: a newcomer can tell how to run the project and where to lookevidence: file README.md, snapshot of 8 October 2026
  • make a commit soon+5
  • commit more often+5
  • spread work across more weeks instead of bursts+5
  • publish a release or tag a version+5
  • 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
  • bring in a second maintainer+2
  • share the work with other contributors+2
  • add a contributing guide+1
  • set up a branch protection policy+1
  • write meaningful commit messages+1