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

applicable weight 80%

nphne-mbzqippq/great-grove-1-0

Language: TSX
branch main

Vibe project: great-grove

Open on SourceCraftDownload report (Markdown)snapshot 8 October 2026signal coverage 80%analysed 17 September 2026 at 22:38 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 practicessignal coverage 76%
11.4–17.4 / 25
partial
Project activity
7.4 / 25
scored
Securitywill appear with a member token
no data
CI/CDsignal coverage 60%
7.5–15 / 18.8
partial
Issues
16.4 / 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: tests directory, docs directory, contributing guide, 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
  • SourceCraft CI is configured
  • The build is described by a Dockerfile
  • Dependency versions are pinned
  • Review is required before merge
  • The main branch is protected

What affected the score

Penalties

Documentation and best practices

  • −5
    README1 chars, no quickstart
  • −2
    license filemissing
  • −<1
    share of short commit messages — 20%

Project activity

  • −4
    top author's share of commits — 100%
  • −4
    unique authors — 1 author
  • −4
    last releaseno releases or version tags
  • −3
    weekly activity — 1 week
  • −2
    commits in the last year — 5 commits
  • −1
    last commit — 75 days

CI/CD

  • −4
    CI configuration contents

Issues

  • −2
    age of open issues — 75 days1 issue

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 −2
    tests directorydata not collected
  • up to −2
    docs directorydata not collected
  • up to −1
    contributing guidedata not collected

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
  • Documentation
    +5
    add a quickstart section to the READMEREADMEwhy: a newcomer can tell how to run the project and where to lookevidence: file README.md, snapshot of 8 October 2026
  • 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
  • publish a release or tag a version+4
  • run CI on pull requests, not only on pushes to the default branch+4
  • spread work across more weeks instead of bursts+3
  • add a license file+2
  • work through the stale open issues+2
  • commit more often+2
  • make a commit soon+1
  • write meaningful commit messages+<1