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

applicable weight 80%

yuri-vashchenko/python-projects-cmdpal-extension

Language: C#
branch main
Open on SourceCraftDownload report (Markdown)snapshot 8 October 2026signal coverage 80%analysed 17 September 2026 at 22:17 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.1 / 25
scored
Project activity
24.5 / 25
scored
Securitywill appear with a member token
no data
CI/CDsignal coverage 60%
11.3–18.8 / 18.8
partial
Issues
16.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
  • Issues are closed quickly (today)
  • Commits span the whole year (133 commits)

What affected the score

Penalties

Documentation and best practices

  • −2
    tests directorymissing
  • −2
    Dockerfilemissing
  • −2
    dependency lockfilemissing
  • −2
    review policyno protection
  • −1
    contributing guidemissing
  • −1
    branch protection policyno protection

Project activity

  • −<1
    last commit — 49 days
  • −<1
    last release — 49 days

Issues

  • −2
    age of open issues — 89 days38 issues
  • −<1
    issue resolution time — today38 issues

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
  • Documentation
    +2
    write tests for the projecttests directorywhy: the build and the checks are reproducible for whoever takes the code
  • Documentation
    +2
    containerize the project — add a DockerfileDockerfilewhy: a newcomer can tell how to run the project and where to look
  • Documentation
    +2
    add a dependency lockfiledependency lockfilewhy: the build and the checks are reproducible for whoever takes the code
  • set up a review policy+2
  • work through the stale open issues+2
  • add a contributing guide+1
  • set up a branch protection policy+1
  • make a commit soon+<1
  • publish a release or tag a version+<1
  • close issues faster+<1