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

applicable weight 80%

mail-ashatrov-ru/test197

Language: Python
branch main
Open on SourceCraftDownload report (Markdown)snapshot 8 October 2026signal coverage 80%analysed 2 October 2026 at 21:43 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
10.1 / 25
scored
Securitywill appear with a member token
no data
CI/CDsignal coverage 60%
11.3–18.8 / 18.8
partial
Issues
18.8 / 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
  • Open issues do not pile up (6 days)
  • Almost no marked debt in the code
  • SourceCraft CI is configured
  • The README introduces the project
  • Commits are fresh (13 days)

What affected the score

Penalties

Documentation and best practices

  • −2
    license filemissing
  • −2
    docs directorymissing
  • −2
    dependency lockfilemissing
  • −2
    review policyno protection
  • −1
    contributing guidemissing
  • −1
    branch protection policyno protection

Project activity

  • −4
    top author's share of commits — 100%
  • −4
    unique authors — 1 author
  • −4
    last releaseno releases or version tags
  • −2
    weekly activity — 2 weeks
  • −1
    commits in the last year — 16 commits

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
    share the work with other contributorstop author's share of commits — 100%why: the work does not rest on a single person
  • Activity
    +4
    bring in a second maintainerunique authors — 1 authorwhy: the work does not rest on a single person
  • Activity
    +4
    publish a release or tag a versionlast releasewhy: the build and the checks are reproducible for whoever takes the code
  • add a license file+2
  • write project documentation+2
  • add a dependency lockfile+2
  • set up a review policy+2
  • spread work across more weeks instead of bursts+2
  • add a contributing guide+1
  • set up a branch protection policy+1
  • commit more often+1