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

applicable weight 80%

juwain/hc-private-probe

Language: JavaScript
branch main

Приватный репозиторий-проба для приёмки Repo Health Score: проверка, что данные закрытого репозитория не попадают на публичную поверхность

Open on SourceCraftDownload report (Markdown)snapshot 8 October 2026signal coverage 80%analysed 28 September 2026 at 21:52 UTC — not all categories measured

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 practices
16.4 / 25
scored
Project activity
17.5 / 25
scored
Securitywill appear with a member token
no data
CI/CDsignal coverage 60%
11.3–18.8 / 18.8
partial
Issues
18.8 / 18.8
scored
Code health
12.5 / 12.5
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

Strengths

what's already done
  • Open issues do not pile up (10 days)
  • Almost no marked debt in the code
  • SourceCraft CI is configured
  • The README introduces the project
  • Commits are fresh (11 days)

What affected the score

Penalties

Documentation and best practices

  • −2
    docs directorymissing
  • −2
    Dockerfilemissing
  • −2
    review policyno protection
  • −1
    branch protection policyno protection
  • −<1
    share of short commit messages — 25%

Project activity

  • −2
    unique authors — 2 authors
  • −2
    commits in the last year — 4 commits
  • −2
    weekly activity — 2 weeks
  • −2
    top author's share of commits — 75%

Not measured — interval width

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

CI/CD

  • up to −8
    CI runsdata not collected

What will raise the score

by strength of impact
  • Documentation
    +2
    write project documentationdocs directorywhy: a newcomer can tell how to run the project and where to look
  • Documentation
    +2
    containerize the project — add a DockerfileDockerfilewhy: a newcomer can tell how to run the project and where to look
  • Documentation
    +2
    set up a review policyreview policywhy: a change is reviewed, and the history stays readable
  • bring in a second maintainer+2
  • commit more often+2
  • spread work across more weeks instead of bursts+2
  • share the work with other contributors+2
  • set up a branch protection policy+1
  • write meaningful commit messages+<1