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

applicable weight 65%

balabza/lisa-water-pipeline-showcase

Language: TypeScript
branch main

Водопровод · Демонстратор

Open on SourceCraftDownload report (Markdown)snapshot 8 October 2026signal coverage 65%analysed 8 October 2026 at 21:28 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. The rest share their weight for now.

Six categories

earned / weight
Documentation and best practicessignal coverage 95%
24.8–26.3 / 30.8
partial
Project activity
28.8 / 30.8
scored
Securitywill appear with a member token
no data
CI/CDsignal coverage 60%
12–21.2 / 23.1
partial
Issuesthe tracker is empty or not set up
no data
Code health
15.4 / 15.4
scored
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: contributing guide
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
  • Almost no marked debt in the code
  • SourceCraft CI is configured
  • The README introduces the project
  • Commits are fresh (today)
  • Commits span the whole year (35 commits)

What affected the score

Penalties

Documentation and best practices

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

Project activity

  • −1
    unique authors — 3 authors
  • −1
    weekly activity — 5 weeks
  • −<1
    top author's share of commits — 51%
  • −<1
    last release — 31 days

CI/CD

  • −2
    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

Documentation and best practices

  • up to −1
    contributing guidedata not collected

CI/CD

  • up to −9
    CI runsdata not collected

What will raise the score

by strength of impact
  • Documentation
    +3
    set up a review policyreview policywhy: a change is reviewed, and the history stays readable
  • CI/CD
    +2
    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
    +1
    set up a branch protection policybranch protection policywhy: a change is reviewed, and the history stays readable
  • bring in a second maintainer+1
  • spread work across more weeks instead of bursts+1
  • share the work with other contributors+<1
  • write meaningful commit messages+<1
  • publish a release or tag a version+<1