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

applicable weight 80%

yndx-bulanna-6oiifj/maigret

branch main
imported from GitHub
Open on SourceCraftDownload report (Markdown)snapshot 8 October 2026signal coverage 80%analysed 25 September 2026 at 21:44 UTC — part unavailable

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
21.4 / 25
scored
Project activity
24.7 / 25
scored
Securitywill appear with a member token
no data
CI/CDsignal coverage 60%
7.5–15 / 18.8
partial
Issues
18.8 / 18.8
scored
Code health
0–12.5 / 12.5
collection failed
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
Not measured: TODO/FIXME density
couldn't see it
the platform's window was truncated: a deep file or a recent version may have fallen outside it

Strengths

what's already done
  • Open issues do not pile up (13 days)
  • SourceCraft CI is configured
  • The README introduces the project
  • Commits are fresh (15 days)
  • Commits span the whole year (405 commits)

What affected the score

Penalties

Documentation and best practices

  • −2
    review policyno protection
  • −1
    branch protection policyno protection
  • −<1
    share of short commit messages — 2%

Project activity

  • −<1
    last release — 58 days

CI/CD

  • −4
    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 −8
    CI runsdata not collected

Code health

  • up to −13
    TODO/FIXME densitydata not collected

What will raise the score

by strength of impact
  • CI/CD
    +4
    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
  • Documentation
    +2
    set up a review policyreview policywhy: a change is reviewed, and the history stays readable
  • Documentation
    +1
    set up a branch protection policybranch protection policywhy: a change is reviewed, and the history stays readable
  • publish a release or tag a version+<1
  • write meaningful commit messages+<1