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

applicable weight 55%

zerles4/git-quest-tree

branch main
Open on SourceCraftDownload report (Markdown)snapshot 8 October 2026signal coverage 55%analysed 17 September 2026 at 20:13 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 practices
0 / 36.4
scored
Project activitysignal coverage 33%
1.1–25.3 / 36.4
partial
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: commits in the last year, weekly activity, top author's share of commits, unique authors
data not collected
the surface didn't answer this collection run

Strengths

what's already done

No metric has a full score yet

What affected the score

Penalties

Documentation and best practices

  • −10
    READMEmissing
  • −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
  • −2
    share of short commit messages — 98%

Project activity

  • −6
    last releaseno releases or version tags
  • −5
    last commit — 302 days

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

Project activity

  • up to −6
    commits in the last yeardata not collected
  • up to −6
    weekly activitydata not collected
  • up to −6
    top author's share of commitsdata not collected
  • up to −6
    unique authorsdata 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
  • Documentation
    +10
    add a quickstart section to the READMEREADMEwhy: a newcomer can tell how to run the project and where to look
  • Activity
    +6
    publish a release or tag a versionlast releasewhy: the build and the checks are reproducible for whoever takes the code
  • make a commit soon+5
  • add a license file+3
  • 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
  • add a contributing guide+2
  • set up a branch protection policy+2
  • write meaningful commit messages+2