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

applicable weight 65%

nphne-mbzqippq/lively-garden

Language: TSX
branch main

Vibe project: lively-garden

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

Six categories

earned / weight
Documentation and best practicessignal coverage 90%
26.6–29.6 / 30.8
partial
Project activity
15.3 / 30.8
scored
Securitywill appear with a member token
no data
CI/CDsignal coverage 60%
13.8–23.1 / 23.1
partial
Issuesthe tracker is empty or not set up
no data
Code health
0–15.4 / 15.4
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, 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 README introduces the project
  • CI checks pull requests
  • Commits span the whole year (152 commits)
  • Contributions are spread across authors

What affected the score

Penalties

Documentation and best practices

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

Project activity

  • −4
    last releaseno releases or version tags
  • −4
    share of unanswered pull requests — 100%sample: 10 of 10
  • −4
    share of closed pull requests — 0%window: 50 PRs, sample threshold: 10 of 10
  • −3
    weekly activity — 1 week
  • −1
    unique authors — 3 authors
  • −1
    last commit — 75 days

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 −3
    tests directorydata not collected

CI/CD

  • up to −9
    CI runsdata not collected

Code health

  • up to −15
    TODO/FIXME densitydata not collected

What will raise the score

by strength of impact
  • Activity
    +4
    publish a release or tag a versionlast releasewhy: the build and the checks are reproducible for whoever takes the code
  • Activity
    +4
    respond to pull requestsshare of unanswered pull requests — 100%why: an outside contributor gets an answer, and their work is not lostevidence: the repository's pull request list, snapshot of 8 October 2026
  • Activity
    +4
    close pull requestsshare of closed pull requests — 0%why: an outside contributor gets an answer, and their work is not lostevidence: the repository's pull request list, snapshot of 8 October 2026
  • spread work across more weeks instead of bursts+3
  • set up a review policy+1
  • bring in a second maintainer+1
  • make a commit soon+1
  • write meaningful commit messages+<1