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

applicable weight 55%

superbickov/gitflow

branch main
Open on SourceCraftDownload report (Markdown)snapshot 8 October 2026signal coverage 55%analysed 17 September 2026 at 21: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 segments — Security: will appear with a member token; Issues: the tracker is empty or not set up; Code health. The rest share their weight for now.

Six categories

earned / weight
Documentation and best practicessignal coverage 71%
1–11.4 / 36.4
partial
Project activity
17.8 / 36.4
scored
Securitywill appear with a member token
no data
CI/CDsignal coverage 50%
0–13.6 / 27.3
partial
Issuesthe tracker is empty or not set up
no data
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
Not measured: README
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

No metric has a full score yet

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
  • −2
    contributing guidemissing
  • −2
    branch protection policyno protection
  • −1
    share of short commit messages — 40%

Project activity

  • −6
    last releaseno releases or version tags
  • −3
    last commit — 211 days
  • −3
    unique authors — 2 authors
  • −3
    weekly activity — 2 weeks
  • −2
    commits in the last year — 5 commits
  • −1
    top author's share of commits — 60%

CI/CD

  • −14
    SourceCraft CI configurationmissing

Not measured — interval width

Not a penalty: the lower bound of the score counts the metric as zero, the upper bound as full

Documentation and best practices

  • up to −10
    READMEdata not collected

CI/CD

  • up to −14
    CI runsdata not collected

What will raise the score

by strength of impact
  • CI/CD
    +14
    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
  • Activity
    +6
    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
  • 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
  • make a commit soon+3
  • bring in a second maintainer+3
  • spread work across more weeks instead of bursts+3
  • commit more often+2
  • add a contributing guide+2
  • set up a branch protection policy+2
  • share the work with other contributors+1
  • write meaningful commit messages+1