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

applicable weight 70%

yuri-vashchenko/nix-config

branch main
Open on SourceCraftDownload report (Markdown)snapshot 8 October 2026signal coverage 70%analysed 17 September 2026 at 21:24 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
10.8 / 28.6
scored
Project activity
22.2 / 28.6
scored
Securitywill appear with a member token
no data
CI/CDsignal coverage 60%
11.1–19.7 / 21.4
partial
Issues
21.4 / 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
  • Issues are closed quickly (today)
  • SourceCraft CI is configured
  • The README introduces the project
  • Commits span the whole year (53 commits)
  • Contributions are spread across authors

What affected the score

Penalties

Documentation and best practices

  • −3
    license filemissing
  • −3
    tests directorymissing
  • −3
    docs directorymissing
  • −3
    Dockerfilemissing
  • −3
    dependency lockfilemissing
  • −3
    review policyno protection
  • −1
    contributing guidemissing
  • −<1
    share of short commit messages — 8%

Project activity

  • −5
    last releaseno releases or version tags
  • −1
    last commit — 108 days
  • −<1
    weekly activity — 6 weeks

CI/CD

  • −2
    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 −9
    CI runsdata not collected

What will raise the score

by strength of impact
  • Activity
    +5
    publish a release or tag a versionlast releasewhy: the build and the checks are reproducible for whoever takes the code
  • Documentation
    +3
    add a license filelicense filewhy: the terms of use are stated, not guessed
  • Documentation
    +3
    write tests for the projecttests directorywhy: the build and the checks are reproducible for whoever takes the code
  • write project documentation+3
  • containerize the project — add a Dockerfile+3
  • add a dependency lockfile+3
  • set up a review policy+3
  • run CI on pull requests, not only on pushes to the default branch+2
  • add a contributing guide+1
  • make a commit soon+1
  • spread work across more weeks instead of bursts+<1
  • write meaningful commit messages+<1